CyanogenMod is a free, community built distribution of Lollipop which greatly extends the capabilities of your phone.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This is a highly experimental and unofficial build of CM12 on Xperia TX.
Note that this may be unstable, not booting, missing in features or anything else. Flash at your own risk!
NOTE(20150522):
I got a new phone weeks ago, so TX won't be my daily driver anymore. And this ROM will be discontinued due to limited time and energy. Thanks for your support.
Known bugs:
See post #2
"About phone" screen:
{
"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"
}
Installing instructions:
Flash the ZIP package as usual, then flash the kernel file via fastboot.
A full wipe is recommended before the installation, even if you are coming from last version of CM12.
OLD WAY FOR .IMG FILES:
1. Unzip the system and kernel image
2. Boot the phone into fastboot mode
3. fastboot -i 0xfce flash system system.img
4. fastboot -i 0fxce flash boot boot_f.elf
5. fastboot -i 0xfce reboot
6. Get into recovery at once and wipe data & cache
7. Reboot. The first boot may take very long time.
DESCRIPTION ABOUT INTERNAL STORAGE PERMISSION
ATTENTION:
CM has changed owner of internal storage to 1023:1023 (media_rw:media_rw). This is the default value in AOSP, but different from the one in Sony stock ROMs. I'm considering changing to 1023:1023 in my unofficial builds as well, but I want to hear your opinion first.
Advantage of 1023:1023 is: it's default in AOSP, using this will solve some problems in AOSP-derived ROMs (e.g. moving apps to sdcard may fail with "insufficient space" error. And maybe some more...)
Drawback of 1023:1023 is: it's incompatible with other ROMs. If you switch to other ROMs without changing owner back, you won't be able to write into internal storage, just like those who formatted int storage in 5.0 or recovery.
Advantage and disadvantage of 2800:2800(Sony stock) are the the way round... better compatibility but cause problems with AOSP.
(Changing owner only takes a few lines of code. That's easy)
So which one do you prefer? 1023:1023 or 2800:2800? Please leave your opinion in the reply. Thanks~
20150312- have 2800:2800. 20150319+ have 1023:1023.
Click to expand...
Click to collapse
Download:
NOTE: sdcard owner has been changed to 1023:1023 since 20150319.
If you want to switch to other ROMs, remember to do this before you flash in order to get a writable internal storage.
Code:
su
busybox chown -R 2800:2800 /mnt/media_rw/sdcard0
20150521
https://drive.google.com/file/d/0BwkmhbR5VHpAQmNhWE9IcUJYRXM/view?usp=sharing
OLD VERSION:
20150514
https://drive.google.com/file/d/0BwkmhbR5VHpAOUp0VzJva3BabjA/view?usp=sharing
20150508
https://drive.google.com/file/d/0BwkmhbR5VHpAS3JqdW9YWUkyVms/view?usp=sharing
20150501
https://drive.google.com/file/d/0BwkmhbR5VHpARUFLdTlXM090Zk0/view?usp=sharing
20150424
https://drive.google.com/file/d/0BwkmhbR5VHpAeEhJeC1WcFVYYVk/view?usp=sharing
20150418
https://drive.google.com/file/d/0BwkmhbR5VHpASjIxbVBYQ2R3am8/view?usp=sharing
20150410
https://drive.google.com/file/d/0BwkmhbR5VHpARzBIaFIwbE5Qak0/view?usp=sharing
20150404
https://drive.google.com/file/d/0BwkmhbR5VHpAYmdPLUd2UGNBbTg/view?usp=sharing
20150402
https://drive.google.com/file/d/0BwkmhbR5VHpAVkxWRmx0bWh4X2s/view?usp=sharing
20150325
https://drive.google.com/file/d/0BwkmhbR5VHpAcjdRNU11NUpEanM/view?usp=sharing
NOTE: Screen will go out if brightness is set to minimum. Fix is in the attachment (lights.msm8960.so.zip) Extract this to /system/lib/hw and it will be OK.
20150319
https://drive.google.com/file/d/0BwkmhbR5VHpAWWtCQ1FEOHVaMms/view?usp=sharing
20150312
https://drive.google.com/file/d/0BwkmhbR5VHpAWnM2RnNzVXFwbUk/view?usp=sharing
Rec and permission fix: https://drive.google.com/file/d/0BwkmhbR5VHpAV0ZPUW9RZjF1RXM/view?usp=sharing
Step 1. FIash the ROM zip
Step 2. Flash kernel in fix
Step 3. Put system folder in fix.7z to the phone
(IF YOU HAVE FLASHED BEFORE APPLYING FIX) Step 4. Execute these commands in adb shell/Terminal Emulator
Code:
su
chown 2800:2800 /mnt/media_rw/sdcard0
If you find these instructions hard to understand, you may try this flashable zip by Antiga Prime. Thanks!
20150302
https://drive.google.com/file/d/0BwkmhbR5VHpAa0ZtSXQ5UUxuQ2M/view?usp=sharing
20150128
https://drive.google.com/file/d/0BwkmhbR5VHpARW0xQkswWE5aOWs/view?usp=sharing
20150123
https://drive.google.com/file/d/0BwkmhbR5VHpAM0c2SHd5TzVlems/view?usp=sharing
20150110
https://drive.google.com/file/d/0BwkmhbR5VHpAWkUyTHhqS1M1Nnc/view?usp=sharing
20150103
https://drive.google.com/file/d/0BwkmhbR5VHpANi1UVG1YbVJoQlk/view?usp=sharing
Kernel with TWRP bug fixed: https://drive.google.com/file/d/0BwkmhbR5VHpATjBvblRBU05VbXM/view?usp=sharing
20141226
https://drive.google.com/file/d/0BwkmhbR5VHpANFhTdzQyQTJEUmc/view?usp=sharing
No more separate kernel
20141219
System: https://drive.google.com/file/d/0BwkmhbR5VHpAX25JbXFVRWJxMjQ/view?usp=sharing
Kernel: https://drive.google.com/file/d/0BwkmhbR5VHpAWE5jQUc5aFR2Q28/view?usp=sharing
Cyanogen Recovery is able to install from internal storage now, but it requires signature verification. The kernel file contains Cyanogen recovery without that verification process. Next time this will be merged into system zip file and there will be no more standalone kernel image.
20141212
Kernel: https://drive.google.com/file/d/0BwkmhbR5VHpAYktOYTA1RnJtam8/view?usp=sharing
System: https://drive.google.com/file/d/0BwkmhbR5VHpAZXRockhtY1V0STA/view?usp=sharing
20141207
System: https://drive.google.com/file/d/0BwkmhbR5VHpAcFVYUWpwenhrVnc/view?usp=sharing
Kernel: https://drive.google.com/file/d/0BwkmhbR5VHpAbUF0LVAybm9ZVGs/view?usp=sharing
20141205
System (Google Drive): https://drive.google.com/file/d/0BwkmhbR5VHpAX2VaNUdPUUtTVU0/view?usp=sharing
My removable disk is not with me at this moment, so I couldn't make a TWRP included kernel. Kernels from previous versions should be compatible though.
Kernel (Google Drive): https://drive.google.com/file/d/0BwkmhbR5VHpAUVp2azBRX1VRR28/view?usp=sharing
20141203
Kernel (Google Drive): https://drive.google.com/file/d/0BwkmhbR5VHpAUXA1OXFnakZOZ0U/view?usp=sharing
System (Google Drive): https://drive.google.com/file/d/0BwkmhbR5VHpAbXhXVDRpOFFQQ2s/view?usp=sharing
20141130
System: http://pan.baidu.com/s/1o6LWX5K
Google Drive: https://drive.google.com/file/d/0BwkmhbR5VHpAQjdUcG1RbGxmQms/view?usp=sharing
Kernel: http://pan.baidu.com/s/1gdovtnl
Google Drive: https://drive.google.com/file/d/0BwkmhbR5VHpAcW1GbmF6cVRNSEU/view?usp=sharing
NOTE: Build time and CyanogenMod version in About Phone are not changed. They will when I get enough time to make a clean build.
20141128
System: http://pan.baidu.com/s/1qWCzw4W
Google Drive: https://drive.google.com/file/d/0BwkmhbR5VHpAdUtabGdVblJ3Njg/view?usp=sharing
Kernel: http://pan.baidu.com/s/1qWwQuhm
Google Drive: https://drive.google.com/file/d/0BwkmhbR5VHpAbFo5UDM1VzJSRjA/view?usp=sharing
No standalone kernel from now on. CM's custom recovery has been included (and it's tap-able )Seems not finished yet.
And Superuser has been integrated as well. No need for other apps.
20141127
System ZIP: http://pan.baidu.com/s/1jG3inaQ
Kernel: http://pan.baidu.com/s/1mgBlDgs
Google Drive mirror(kernel): https://drive.google.com/file/d/0BwkmhbR5VHpAYVdMNXVEZDNXZEk/view?usp=sharing
Google Drive mirror(system): https://drive.google.com/file/d/0BwkmhbR5VHpAeGJlakhLc3lYNGM/view?usp=sharing
(Included a unit test app for messaging by mistake, just delete it)
20141125:
System ZIP: http://pan.baidu.com/s/1mgkho5E
Kernel: http://pan.baidu.com/s/1bnm1xV5
20141121:
System ZIP (Recovery flashable): http://pan.baidu.com/s/1i37nOTf
Kernel (Flash after the system - reboot to bootloader in Recovery after flashing the zip above): http://pan.baidu.com/s/1pJHQYld
Initial ver
System image: http://pan.baidu.com/s/1B5Ofk
Kernel: http://pan.baidu.com/s/1nt0ua9N
Device specific sources are on my GitHub (updateing), and kernel is built on kernel-msm repo listed there.
Changelog (FROM UPSTREAM)
20150521
FM Transmitter enabled (it's so lucky that (it seems) only our device fully supports it)
20150514
->post #2
20150508
mainly upstream changes
20150501
->post #2
20150424
Android 5.1.1
-> post #2
new WiFi driver
20150418
workaround about flickers in some apps -> post #2
20150410
-> post #2
20150404
goodbye Microsoft
try to fix abnormal record of battery comsumption of mobile network
20150402
first Android 5.1 build
20150325
Xperia logo functions normally when a notification is cleared when screen is off
20150319
changed internal storage permission to 1023:1023
upstream changes
-> post #2
20150312
upstream changes. (one noticable feature: LiveDisplay)
20150302
upstrem changes
added a FM radio app, but it's not working now.
20150128
-> post #2
mostly upstream features and fixes (new wallpaper, setup wizard, etc)
20150123
-> post #2
theme engine (upstream)
no more sudden change of brightness when turning screen off
SELinux enforcing (mostly upstream with minor changes for TX)
more customization
20150110
mostly upstream changes
20150103
TWRP included (built from source, not a copy of Kitkat kernel. I didn't realize CM Recovery was not meant for custom ROMs...)
-> post #2
20141226
Android 5.0.2
USB Mass Storage support (Settings-Storage-(3dot menu))
-> post #2
20141219
-> post #2
weather shown in status bar
Gallery is materialized
Battery icon selection
20141212
-> post #2
more materialization
icon fixes
20141207
some features from upstream, such as vibrator intensity control
show network mode in network search result
-> post #2
20141205
Mostly upstream fixes, e.g. appearance of Settings app, clickable time & date
Reduced some unused kernel modules
Select dlmalloc as memory allocator. It's jemalloc in previous versions, but fusion3 have dlmalloc choosen. Let's see what will happen... (seems smoother)
20141203
Android 5.0.1
fix: (post #2)
20141130
upstream fixes and new features
TEST: one case about working GPS in post #2
20141128
fix: (in post #2) and some info about GPS
new: CM's handsome recovery
new: integrated Superuser
20141127
fix: (in post #2)
20141125
fix: (in post #2)
new: Message app
new: a small number of personalization settings (quick pulldown etc)
20141121
fix: data and WiFi icon movement
fix: no audio
fix: NFC Service FC
fix: Download / Documents / Call History FC
new: full set of fonts
new: multi user support / Guest Mode
Credits:
Finally thanks CyanogenMod team who merged sources so quickly, and Sony who made all this happen, and a lot more on Gerrit who helped me solve the compliation errors.
One possible bug: no sound. Extract the attached file to /system/etc
If there's nothing wrong, you can ignore this. I can't remmeber if I inlcuded this in the system image...FIXED in 20141121
BUG #2: NFC Service FC after boot. -> Delete /system/etc/permissions/android.hardware.nfc.hce.xml via Recovery (mount /system first)FIXED in 20141121
BUG #3: GApps not working -> Try Gapps in this post
BUG #4: Download and Call History FC.FIXED in 20141121
BUG #5: WiFi hotspot doesn't turn on.FIXED in 20141125
BUG #6: Camera stops working after switching user. -> Delete /data/camera/cache_data.dat and (in terminal emulator) su && pkill mediaserver DIRTY FIX in 20141127
BUG #7: GPS satellites are found but can't get lock -> PLEASE TEST! After every step, try if it can get a lock in 2 mins. If not, do next step and reboot.
1. Add "QUIPC_ENABLED=0" at the end of /etc/gps.conf <- Some successful reports.
2. Set "INTERMEDIATE_POS" to 1, uncomment "ACCURACY_THRES", and set "ACCURACY_THRES" to 1000 (this is the target accuracy - choose as you like)
3. Comment out ACCURACY_THRES STEP 1 INCLUDED SINCE 20141203
BUG #8: Contacts -> Menu -> Import/Export -> Import from storage FC FIXED in 20141125
BUG #9: Dialer -> Call History -> Menu -> Clear Call Logs -> (Select some) -> OK FC FIXED in 20141125
BUG #10: FC when receiving SMS via native Messaging app. Hangouts works though. EMERGENCY FIX: http://pan.baidu.com/s/1gdeRIbL push to /system/priv-app/Mms FIXED in 20141127
BUG #11: Moving 2 apps to internal storage will fail on the second one. SEEMS FIXED (20150123)
BUG #12: Call diverting can't be set After many tries I found this was not a bug of this ROM. It's the network operator to blame. I inserted my SIM to an ancient Nokia and it couldn't set call diverting either. And when I inserted an SIM which had been confirmed that call diverting was working, the settings in this ROM would also work without any problem.
BUG #13: Hanging up when an outgoing call is still ringing will cause Dialer FC. -> Put http://pan.baidu.com/s/1gd28sjp into /system/priv-app/DialerFIXED in 20141128
BUG #14: Audio quality over Bluetooth is terrible. The sound is "slowed down" and pops over time. This fixes A2DP audio quality, but causes phone calls to fail when BT headset is connected. So if you use this phone and BT headset/carkit as daily driver, please replace /system/etc/audio_policy.conf with the one in previous version (or the one in attachment) INFO(FROM 20141219)Bluetooth call and music are all OK now, but there's something that has to be done in order to get music working: make a call when BT headset is connected. You can call any self-service number and hang up after connected. Otherwise the audio quality will still be terrible...
BUG #15: FC when selecting Clock -> Alarms -> (select profile) FIXED in 20141203
BUG #16: Error when finishing manual search for mobile networks FIXED in 20141203
BUG #17: After receiving MMS, default Messaging app will crash. (Hangouts is working) FIXED IN 20141207
BUG #18: Volume keys are not usable when screen is off.Works as we expect now.
BUG #19: User switching is broken (reboot and cannot switch to desired user) Can't reproduce this on 20150103
BUG #20: BT audio is broken... again.(just as well that this only happens when NuPlayer is is use. - I doubt whether we should use this on this old hardware platform) -> Turn NuPlayer off in Development Settings, then look at BUG #14
BUG #21: Music files on int/ext sdcards can't be selected as ringtone (plays a beep). Turning SELinux to permissive solves this.REPORTED FIXED in 20150514, don't know when it got fixed
BUG #22: FM Radio produces no sound.FIXED in 20150514. Note that FM will still remain on when you remove the headphones but no signal can be picked up under such circumstance.
BUG #23: USB Mass Storage is not working. Shows a drive w/o disc on PC. FIXED in 20150319
BUG #24: (Android 5.1) Glitches in some apps, e.g. Fuubo (a Sina Weibo client) (gone with battery saver activated. The animation is still shown but no glitches) WORKAROUND: Add this line to build.prop debug.hwui.render_dirty_regions=false FIXED in 20150424
BUG #25: Mute and hold button in call screen are missing/disabled FIXED in 20150410
BUG #26: Due to new WiFi driver, MAC address will be changed. Will fix in next build. FIXED in 20150501
Amazing! Thanks a lot!
I've sold TX months ago. Now I have a Xperia T. I hope I can try a Lollipop T ROM soon!
DS-1 said:
Amazing! Thanks a lot!
I've sold TX months ago. Now I have a Xperia T. I hope I can try a Lollipop T ROM soon!
Click to expand...
Click to collapse
Thanks for your support
Oh, no: thanks to you! You're doing something really special for our abandoned phones!
By the way, I can't try it on my T, but how's the first feeling with this new rom? What are your first impressions?
updateing said:
Thanks for your support
Click to expand...
Click to collapse
updateing said:
One possible bug: no sound. Extract the attached file to /system/etc
If there's nothing wrong, you can ignore this. I can't remmeber if I inlcuded this in the system image...
BUG #2: NFC Service FC after boot. -> Delete /system/etc/permissions/android.hardware.nfc.hce.xml via Recovery (didn't pack this in...)
Click to expand...
Click to collapse
Thanks for the rom. I can't find /etc/permissions/android.hardware.nfc.hce.xml, when I go into file manager from recovery only system/bin is shown, what to do?
icALASAD said:
Thanks for the rom. I can't find /etc/permissions/android.hardware.nfc.hce.xml, when I go into file manager from recovery only system/bin is shown, what to do?
Click to expand...
Click to collapse
Mount system partition via recovery before entering aroma file manager. :good:
@updateing
Great work!! Gonna give this a shot for XV :good:
Will try to compile with your sources on git. Any recommendations?
WhiteNeo said:
Mount system partition via recovery before entering aroma file manager. :good:
@updateing
Great work!! Gonna give this a shot for XV :good:
Will try to compile with your sources on git. Any recommendations?
Click to expand...
Click to collapse
Thanks, it works.
I've installed PA GApps for Android 5.0 and I'm getting a few app crashes here and there. Downloads/Documents doesn't work at all, Google+ can't connect to the server for some reason, Play Newsstand crashes (downloaded from Play Store) and few things like that. Should I be posting these bugs? Are they rom related or is it because of GApps package?
Also, root works. I'll wipe everything and clean install GApps, see how it goes. Everything crashes for some reason right now.
icALASAD said:
Thanks, it works.
I've installed PA GApps for Android 5.0 and I'm getting a few app crashes here and there. Downloads/Documents doesn't work at all, Google+ can't connect to the server for some reason, Play Newsstand crashes (downloaded from Play Store) and few things like that. Should I be posting these bugs? Are they rom related or is it because of GApps package?
Click to expand...
Click to collapse
Might try the gapps from here.. Link
In other devices' forums, I have read about rom-related issues with certain google apps. So might possibly be rom related..
A logcat of the issues might come in handy.
WhiteNeo said:
Might try the gapps from here.. Link
In other devices' forums, I have read about rom-related issues with certain google apps. So might possibly be rom related..
A logcat of the issues might come in handy.
Click to expand...
Click to collapse
Downloading this right now, I'll see how it goes and let you know asap.
---------- Post added at 09:38 PM ---------- Previous post was at 08:38 PM ----------
Hmm... Downloads/Documents doesn't seem to work. I've cleaned everything and installed rom and gapps from scratch, music didn't work at first, but then I applied the fix and it's working now, DSP manager started working too. Every crash I had seems to be gone, for now at least. Only problem remains Downloads, tried cleaning data, but doesn't help. SuperSU BETA did work, I was able to root it by just flashing zip in recovery. All in all this rom's pretty stable considering that it's an experimental for now.
Also multiple users doesn't work, when you click on that profile icon in the right corner of notification dropdown it just opens up your LOCAL profile, not even the Google one.
---------- Post added 21st November 2014 at 12:03 AM ---------- Previous post was 20th November 2014 at 11:10 PM ----------
And also this
---------- Post added at 12:54 AM ---------- Previous post was at 12:03 AM ----------
Also dialer crashes when I go to history tab.
icALASAD said:
Downloading this right now, I'll see how it goes and let you know asap.
---------- Post added at 09:38 PM ---------- Previous post was at 08:38 PM ----------
Hmm... Downloads/Documents doesn't seem to work. I've cleaned everything and installed rom and gapps from scratch, music didn't work at first, but then I applied the fix and it's working now, DSP manager started working too. Every crash I had seems to be gone, for now at least. Only problem remains Downloads, tried cleaning data, but doesn't help. SuperSU BETA did work, I was able to root it by just flashing zip in recovery. All in all this rom's pretty stable considering that it's an experimental for now.
Click to expand...
Click to collapse
Yes the download manager and dialer are confirmed bugs. I'll sync and make a new build to see if they are fixed.
I'll try adding multi-user support in this build.
You really keep the hard work @updateing
=)
Thank you for bring Lollipop taste to TX user
xD
Wi-Fi icon moves back and forth in status bar when little arrows show up and in Settings some menus have the same icon, like 'Buttons' and 'Home' have the same house icon, also 'Profiles' and 'Location' both have location icon.
icALASAD said:
Wi-Fi icon moves back and forth in status bar when little arrows show up and in Settings some menus have the same icon, like 'Buttons' and 'Home' have the same house icon, also 'Profiles' and 'Location' both have location icon.
Click to expand...
Click to collapse
Will fix in next build. Thanks!
EDIT: wait for upstream to fix the icons in settings...
Great....we have Lollipop build....
i will try it when the bugs is not affecting much on my daily usage
Thanks for the update. Should I install it on clean phone or just upgrade? Also camera button doesn't work
Sorry, but is there any firm hope that we will have this on T (mint)?
tajimura said:
Sorry, but is there any firm hope that we will have this on T (mint)?
Click to expand...
Click to collapse
I am asking myself the same. There are some roms T/TX compatible. Out World be great having Android L on XT.
tajimura said:
Sorry, but is there any firm hope that we will have this on T (mint)?
Click to expand...
Click to collapse
mint is officially supported by CM, don't worry
Related
** As i don't have HTC Legend anymore, i won't be able to port and share any ROM for Legend anymore. So, anyone are welcome to kang, modified, enhance or whatever you like to this ROM. Just make sure you give appropriate credits ESPECIALLY to the creator of ROM based that i ported over. Best Regards. **
About
As some of you know, several few days ago, i have put an efforts to port Miuiv4 to our device. I'm not a developer, just doing some simple mods but i'm dying to see miuiv4 to run in our device and to see how other device that have similiar hardwares with our legend have motivate me. Now, i have fixed most of the issue and given permissions to share it with you all.
I have put the links to ROM that i take as base so please go there and hit thanks to the respective devs to show our appreciation to their hardwork.
I appreaciate any suggestions but requests are not welcome at all.. I do it for you for free..
Screenshots:
Click to expand...
Click to collapse
Installation
1. Download the ROM zip file
2. Put into your sd card
3. Boot into CWM
4. Do backup (MUST!)
5. FORMAT /boot, /system, /cache, /data if do clean installation. Skip if want to flash on top of 2.7.6
6. Flash the ROM
You also can install from ROM Manager (2.7.6). Thanks to OZNER93 for the testing.
Working Lists (2.9.21):
1. Phone (call/sms)
2. Bluetooth
3. wifi
4. themes (local/online/mixed/backup)
5. camera (normal / panorama)
6. vibrate
7. google account sync
8. play store
9. Miui Toolbox
10. root access
11. screenshot
12. Flashlight (from launcher and from lockscreen
13. Miui Prevent Misuse mode (screen will be locked is prox sensor detected something covering it while phone being unlocked)
14. Google Now tested working. Not included. Get it from its thread
15. Many other upstream Miui features
Not working (2.9.21):
1. everything that doesn't work in cm9 also doesn't work
2. Usb tether
3. Headset
4. please report
Issues+Hints (2.9.21)
1. When applying theme, statusbar doesn't get themed completely, you need to reboot after that
2. When applying statusbar Mod from Miui Toolbox, your statusbar will disappear for a while and your phone seems hang, let it until your phone self reboot.
3. Be sure to clear RAM (long press home button) after do multitasking to avoid random reboot.
4. Total size of internal memory in Settings -> About is not correct.
5. Cursor in composing text for sms is not clearly visible in portrait mode.
6. Launcher
{
"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"
}
1st time boot, it will look weird. Press menu button -> Launcher settings, change grid layout type to 4x4.
Turn off icon shadow to save RAM.
7. Miapps
Backup app is removed from ROM. If you need it, take the apk files attached and push both of it to /system/app/
8. If you keep facing issue after rebooting phone, freeze/remove LBE Guard using titanium backup or using root explorer, it is problematic miapps. I should remove it from ROM by default.
Working Lists (2.7.6):
1. Phone (call/sms)
2. Bluetooth
3. wifi
4. themes (local/online/mixed/backup)
5. camera
6. vibrate
7. google account sync
8. play store
9. miui backup
10. root access
11. screenshot
12. soft nav-bar (enable in ics control panel and do Hot reboot; long press power -> reboot -> Hot Boot and you can rearrange its position in settings -> full settings -> Button -> customize screen key position)
13. adb
14. oc (use third party apps like no-frills cpu)
15. Swipe to clear notifications
16. etc etc.... [lazy mode ;p ]
Not tested (2.7.6):
1. Gps
2. vpn
Not working (2.7.6):
1. everything that doesn't work in cm9 also doesn't work
2. torch (please use third party apps)
3. some options in ics control panel (overscroll effect and app drawer)
4. Usb tether
5. please report
Hints:
A. Turn off animation and set background process limit to "at most 4 processes" in developer options for better performance.Turn off "show rounded corners also might help a little.
B. If you get an annoying popup every time you reboot that saying "export internal data to sd card" as per screenshot below,
this will happen when you try to open Themes while your sdcard still not fully mounted.
To fix it,
1. open root explorer
2. go to /data/sdcard/
3. there will be one empty folder named MIUI (make sure it is really empty first)
4. delete it.
you also can do it via recovery
1. adb shell
2. cd /data/sdcard/
3. rm -r MIUI
now that annoying pop up wont appear again
Change dpi
1. Use root explorer or adb
-from root explorer, go to /system/
-mount r/w
-edit in text editor build.prop
-find ro.sf.lcd_density = 133
-change to 132, or default 160 or whatever value that you prefered
-save changes
-reboot
2.using adb
-pull build.prop
adb pull /system/build.prop
Click to expand...
Click to collapse
-make same changes as above method to it
-push back to /system
adb push build.prop /system/
Click to expand...
Click to collapse
Camera
If camera hang/freezed, go to Settings -> apps -> all, clear data for camera. 1st time launch will take a while. Be patient.
Attached are the Miui Camera. Install as normal app. Load faster but panoramic mode is not working. Upon launching it, turn it off (panoramic mode) from setting.
Credits:
(If i forgot to mention you, PLEASE PM ME to include you)
Miui US Team
zeubea for his CM9 HERE as base
Zackconsole for most parts of the ROM including but not limited to Miui Toolbox, frameworks and SystemUI. One of his thread HERE
Henry_01 for his great Miuiv4 2.7.6 here
OZNER93 for testing installing using ROM Manager
Please if you can, go to their thread and press thanks for them before me..
Download Links:
Current:
2.9.21 b5r0 (mediafire)
MD5 SUM: 124a3ce7b3a9c1b452fa1635cda4ffad
** You can flash it on top of 2.7.6,clear cache and dalvik-cache after flash,no need to clear data, i've done it with no issue at all but if you do face any issue, please do clean install.
Older build (just for references):
2.8.3 Alpha
2.7.6 b4r2 download here
2.7.6 b4r1 download here
mediafire link
CHANGELOGS:
26.09.2012
2.9.21 b5r0
- Miui 2.9.21
- Rebased to CM9 Beta 5
- Theme Manager fixed from Miui base
- Torch fixed
- SMS/MMS composing box for dark themes in portrait fixed
- Camera Panorama mode tested working
16.08.2012
2.7.6 b4r2 (Revision 2)
- NEW sound recorder
- NEW Google Quicksearchbox
- UPDATED Notes
- UPDATED Gallery
- Default dpi (160)
- Normal Play Store
15.08.2012
2.8.3 Multi Language Alpha
- Not recommended for daily use, not tested well.
- dpi set to default (160)
- Rebased to Miui 2.8.3
- Usb mount working using UMS app (included), native not working
- Espanol not fully translated (other language not fully tested)
25.07.2012:
2.7.6 b4r1(beta 4 rev 1)
- based on Zeubea's CM9 Beta 4
- dpi still set to 133 by default
- patched play store
- supersu fixed
- graphics bug fixed
- signal bar bug fixed
- added ics control panel
- camera now load up faster
18.07.2012:
- Initial build.
- Based on Zeubea's CM9 Beta 3
- All system packages taken directly from Henry_01's ROM
- added common tweaks (in init.d and sysctl.conf)
- build.prop tweaks
- Graphics bugs
- Signal status bar bugs
- superuser permission issue
reserved
Thx feed3
I will try to install the rom
What is the difference between your rom to rom Miuiv4 Port For Legend - Beta 1.1
---------- Post added at 05:35 AM ---------- Previous post was at 05:27 AM ----------
I get an error message
"E:error in /sdcard/miui-2.7.6-b4-r1.zip (status 6)
installation aborted."
moshe1974 said:
Thx feed3
I will try to install the rom
What is the difference between your rom to rom Miuiv4 Port For Legend - Beta 1.1
---------- Post added at 05:35 AM ---------- Previous post was at 05:27 AM ----------
I get an error message
"E:error in /sdcard/miui-2.7.6-b4-r1.zip (status 6)
installation aborted."
Click to expand...
Click to collapse
Some issue with updater script. maybe got some intermittances during upload. reuploading again now. so sorry..
The differences are some bugs especially graphics glitches are fixed, supersu fully working, ics control panel added and some other things.
Edit: actually that ROM you asked is mine; my initial build.
Link is up in post #2.. I have reupload, then try to download and install it myself, confirm okay now.. enjoy..
Awesome ROM. Installed it and it's running fine. Will keep you posted if I notice anything unusual
Switched back to CM9 because of the graphic bug in the previous build. Testing this now
feed3 hi
Most of the apps i want to install, from the market, say that they are not compatible with my device
have you tried this? http://forum.xda-developers.com/showthread.php?t=1580827
@feed3: more languages would be awesome
s2e not work for me
moshe1974 said:
feed3 hi
Most of the apps i want to install, from the market, say that they are not compatible with my device
Click to expand...
Click to collapse
Did you wipe data before install? I can confirm it is working fine with me. Try clear data for play store and google services framework.
If you didnt like the custom dpi, how if i create one with normal dpi and normal play store. Anyone want it?
Sent from my Legend using xda app-developers app
moshe1974 said:
s2e not work for me
Click to expand...
Click to collapse
I didnt use it as it will shorten my sdcard life span. But lets see if i can find any spare sdcard and try to find any solution possible.
Sent from my Legend using xda app-developers app
Anyone that want to use miui gallery, it is not perfectly scalled for dpi i set. You might want to try to set dpi to 132, can confirm it is better at that dpi. or use cm stock gallery. When i come back from leave, i will attach the apk.
Sent from my Legend using xda app-developers app
xennr3 said:
have you tried this? http://forum.xda-developers.com/showthread.php?t=1580827
@feed3: more languages would be awesome
Click to expand...
Click to collapse
I think i can pull some lang files from cm for other language but i don't know how for other apk that have been completely translated inside the apk inside as what i have done for miui gb previously. Anyone can help on this matter? Credits will be given to you of course and i will add your name into the logo that you saw in settings -> about phones to show my appreciation to you for helping..
Sent from my Legend using xda app-developers app
feed3 said:
Did you wipe data before install? I can confirm it is working fine with me. Try clear data for play store and google services framework.
If you didnt like the custom dpi, how if i create one with normal dpi and normal play store. Anyone want it?
Sent from my Legend using xda app-developers app
Click to expand...
Click to collapse
1 vote for normal DPI here
Feed 3 ty for fix bugs , please try with miui 2.7.20
Supersu Does not recognize the second partition
CAN'T INSTALL LINK2SD APP
feed3 Hello
How to change CPU speed ?
°°°
Attention: This ROM is discontinued!
It still works great as a daily driver and got a large userbase, but as CM10.1 has been abandoned there won't come any new updates anymore!
After working really hard on it for more than 2 month(!) I proudly present my first CM10.1 T-Build :fingers-crossed:
I put lots and lots of effort into it to create a great, smooth and bugfree rom experience for you guys.
I tried to fix all huge bugs on CM10.1 like bluetooth fast forwarding and the wifi hotspot.
Additionally I took the time to create a non-neon gapps package, as the official 4.2 one does only support neon.
{
"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"
}
If you appreciate all the effort that has gone into this ROM then consider a donation.
While it's neither expected nor required it is highly appreciated!
> Paypal Donate link <
Each donator will get a huge thank you and a private dance show
Preview (you can't wait for the leafs getting down now, can you!):
(and as I've been asked a couple times in the past: yes, you can send me an amazon gift card code via PM as wel!)
CM Known Bugs & Fixes:
This list shows what has been done so far.
As you can guess by the sheer amount of the fixed bugs there has been put lots and lots of time into this ROM.
And don't forget about all the awesome work pengus77 has put into the kernel - without him we would still suffer from bsods and huge battery drain.
Do NOT post or ask about stuff on the known bugs list!
The bug is listed here - I don't need to get reminded that it's there.
If there's progress or an ETA or anything we will post about it - if not there's not.
I really mean it! Do not ask, it's just annoying. It might only lead to us abandoning the work on the bug.
Oh check the "plans for the next build" section below as well.
But of course you're very welcome to post a decent fixing idea or development related note in'te the CM10.1 development discussion.
Hall of shame of people who ignored my warnings and still posted about already known bugs.
If someone continuously breaks this threads rules you'll land on my ignore list.
tonyp (damn!)
CM10.1 specific bugs:
Bluetooth is accellerating on many headsets fixed (by replacing the bdroid bt stack with bluez)
Wifi hotspot isn't working fixed (by forwardporting the CM10 internal hotspot handling to CM10.1)
SDCard write speed is subpar. not fixed
bugs affecting all CM10+ based ROMs (unordered list):
unable to reject calls on SU660 basebands fixed
low brightness after unlocking fixed
automatic time on SU660 and v30x basebands is broken fixed
wifi & 3g drain fixed (Kowalski Kernel)
notification lights aren't working fixed
zram is selected at 18% but isn't enabled fixed
init..rc contains some parameters interfering with the kernel configs fixed
bootanimation gets displayed "too long" fixed
CM10.1 Performance CPU settings aren't compatible with our Tegra CPU fixed
you can't bind the searchkey to actions like opening the recent app drawer fixed
FM radio isn't working fixed (see here)
In-Call muting fixed
Call forwarding fixed
autobrightness isn't working properly semi-fixed (kk120+ - kernel instead of ROM controlled, so you can't control it in the ROM, but via a sysfs)
Stock camera has some drawbacks (especially panorama & hdr) semi-fixed (by his or this ported LG Stock camera)
HDMI isn't usable not fixed
no signal after airplane mode bug (double press data or reboot to gain it back) not fixed
Changes and cherrypicks to the CM10.1 codebase:
Major Changes:
The codebase is CM10.1.0 RC4
fixed all the bugs above
incuded tiny non-neon gapps
Development settings enabled by default
Advanced reboot enabled by default
tonyp memory management added and enabled by default
(you can turn it off at Settings - Performance - Memory management)
purgeable assets enabled by default
enabled Pie Controls
Vibrations lowered (no, you can't change it back easily)
removed the autobrightness configuration options
(it's kernel controlled, you can't change it in the ROM!)
removed Videoeditor (and some LWPs)
added the awesome epic Kowalski kernel as prebuilt
(including KowalskiManager, alsa mixer and tx power stuff)
added a ****ing epic easteregg
Cherrypicks:
added more options to rebind the hardwarekey
added more options to the lockscreen longpress buttons
(including screen off! save the power power button some presses!)
option to pull down the Quick Settings panel when there are no new notifications
added a notification drawer brightness slider
option to disable the CRT animation
Center Clock option
Text-only batterystyle
Quickmemo framework support
Option to disable the lockscreen Camera widget
Custom carrier text
Recents RAM bar
much much more - read the changelogs linked at the end of the next post
Plans for future builds:
Bugs fixes:
-
Other:
GCC 4.7 experiments
CREDITS:
arcee and the CM team for all the work they did.
pengus77 for his awesome work at the kernel and new bootloader.
niko (Andrei E.) for his work on including the bluez stack into android.
marsgod for fixing the callbug on the old bootloader.
wkpark for the cracked ICS bootloader, the ramhack idea, and all is valid input.
goo.im, AndroidFileHost and vadonka for providing me great hosting services.
I got a bug - can I report it?:
If you want me to take the time to help and fix your bugs I expect you to take the time and do this properly!
Quick check: Did you do a full wipe before installing build 01? If not you need to do that first!
Check the known bugs section. If it's listed or mentioned there, drop it (and wait patiently if it'll get fixed eventually).
Use the search function and try to find if others have been posted about it.
You're only at the app and can't properly search within a thread?
Then wait until you're at home and report the bug from there!
Check the last 3 pages if the bug has been mentioned there.
You still with me? All of this takes too much of your precious time?
Then use another ROM!
Still nothing? Then report the bug in this thread.
Always attach logs to your bugreport!! Bug reports without logs will get ignored completely.
Study this for more details: [Reference] How to get useful logs
People who fail in doing this properly will get into the hall of shame.
Downloads:
ROM:
By downloading and/or using this ROM you agree to the guidlines of this thread:
Read and understand the entire OP!
Yes, it takes a couple minutes - but what's that compared to the 2+ month I put into the ROM??
Don't be a douchebag!
Follow the rules!
If you agree click the button and download the ROM :fingers-crossed:
Download: http://tonyp.basketbuild.com
Make sure to download the correct version for your bootloader!
Mirror: http://goo.im/devs/tonyp
Gapps:
This ROM already has tiny gapps included! That's a minimum gapps package (<20mb)
I put a lot of effort into integrating the required apps and libs and tested it carefully.
I choose this approach because of the many problems that the standard package causes to our non-neon Tegra2 phone.
Included are only the most basic (g)apps like Playstore, Talk (with working videochat), Calendar sync provicer etc.
If you want to remove the included gapps flash this package after flashing the ROM:
CM10.1-gapps-remover-tonyp.zip
For those of you who want the "full" gapps package including Google Now, TTS, Faceunlock, voice search etc. I worked on a full non-neon gapps package.
Get it from this thread: Non-neon Gapps (Android 4.2) dev-discussion thread
Do NOT flash any other gapps package - they aren't compatible with our phone!
If you accidently did that then format /system and reflash the ROM.
This is necessary to prevent bugs like like the keyboard closing while typing.
Addons:
You can download my officially supported addons from the addons folder:
http://goo.im/devs/tonyp/CM10.1-T-Builds/addons
This ROM has native support for Quickmemo.
For more details read this post.
I've build patches for OpenPdroid and PDroid2.0.
For more details read this post.
Kernel:
kowalski kernel thread
This ROM comes with the awesome kowalski kernel by pengus77.
For new versions (which come regularly) check out his thread!
Various:
TWRP recovery for both bootloaders
my modded adb drivers
Instructions:
Updating to a newer T-Build::
No wipes or system-format needed!
Choose the correct ROM for your bootloader
Flash the ROM
Flash the latest kowalski kernel
Tiny Gapps are included, so there's no need to flash gapps if those are enough for you.
If you want the full gapps package use the non-neon one I provide here.
If you want to remove gapps flash this package after flashing the ROM: CM10.1-gapps-remover-tonyp.zip
Reboot
Coming from another ROM:
If you're on the newbl either use pengus CWM 6.0.2.5 or my TWRP!
Other recoveries won't work.
oldbl users can use any CWM >5 or TWRP version.
Do a full wipe!
Just do the wipe, you will be thankful afterwards when everything does run better.
Format /system
Choose the correct ROM for your bootloader
Flash the ROM
Flash the latest kowalski kernel
Tiny Gapps are included, so there's no need to flash gapps if those are enough for you.
If you want the full gapps package use the non-neon one I provide here.
If you want to remove gapps flash this package after flashing the ROM: CM10.1-gapps-remover-tonyp.zip
Reboot
Don't restore system apps (like Settings) or system data (like Wifi data) with TitaniumBackup!
My personal recommended configuration:
Go to Settings - Performance - Processor and change the "Maximum CPU frequency" to 1200 (or even 1500) and "Set on Boot"
Open the KowalskiManager
enable the 3 power saving options at the top
lower TX Power to 11
Change the SD readaheads to 512
enable dynamic fsync
This ROM comes pre-configured with the following memory management changes:
zRAM enabled with 18%
tonyp memory management enabled
purgeable assets enabled
Changelog:
T-Build 01
T-Build 02
T-Build 03
T-Build 04
T-Build 05
Let me leave with a couple more notes:
This ROMs focus is stability! It's intention is to be a daily driver without the need to constantly flash new updates - that's why I kept you guys waiting that long and didn't release my daily testbuilds (more like 3 builds a day actually) which haven't been perfectly stable, yet.
That's why I took CM10.1 M3 as a base and don't merge in nightly features - everything in this ROM should be well tested and fully working.
I only picked memoryleak fix that's been discovered after M3.
I won't cherrypick each and every feature that's in some other ROM!
If there's a real useful addition that I personally like I will do it, but the fancy stuff has to go into other ROMs.
You guys know me - I am mostly patient and don't mind slight offtopic posts.
For completely offtopic posts you can use the CM 10.1 discussion thread.
... but I hate people who are lazy and don't do their own research. I spent countless hours on this ROM, I think I can expect you to spent a little time before asking questions.
I am not a vendor who's obligated to release a ROM for the phone - I am doing this in my free time for you and me.
So please - don't behave like a total noob. Or [email protected] and I will have a busy fishlapping time
F.A.Q. - Frequently Asked Questions:
How can I swap the mounting points for internal SD card and external SD card?
If you're on the new bootloader, flash this script via Recovery (thanks, @C0D3N1N3R!). For those on the old bootloader, you need this one instead (thanks, @SWTR!).
Which gapps package should I use with this ROM?
Seriously? You haven't been paying attention, have you? Go read the posts above this one!
Which PDroid version should I use?
It's a matter of personal preference, actually. Try both and see which one fits your needs the best. Keep in mind that if you're switching between Openpdroid and PDroid 2.0 (or viceversa) you need to uninstall the app and re-flash the ROM first, or else this kitten will die and it'll be in your conscience forever! I'm serious!!
Just flashed this ROM via recovery and can't get past the boot logo, what's wrong?
Chances are that you're using the wrong Recovery. Try pengus' CMW v6.0.2.5 and flash the ROM again. If the problem persists, check that the ROM zip file isn't corrupted (see each build's md5 hash on tonyp's goo.im CM10.1 folder). If none of that helps, then you better get Tony some logs
How can I know which bootloader my device is using?
An easy way to indentify this is by seeing the bootloader logo that appears when you turn on your device: white -> old bootloader, pink -> new bootloader.
How can I set a custom DPI on this ROM?
You can either use the Google Play DPI Fix Tool, or Tony's personal recommendation: Xposed in combination with Xposed App Settings (link down, use this one or this one instead for now) (see reference by @rugglez).
Viber doesn't work on this ROM, I can't even make a call. What can I do?
According to what we have read, recent versions of Viber won't work on CM 10+ for our device. Apparently, the developers of the app were been notified about the issue and they might look into it soon. Worry not, my friend, since not everything is lost. According to @engine24, Viber version 2.3.6.338 seems to be working alright. Make sure you uninstall your current version of Viber first before installing this one, though!
Battery drain is a bit too high, what's happening?
If you just flashed this ROM, please do one or two full battery charge cycles and see if it helps. Also, check on BetterBatteryStats for rogue apps keeping your device awake (and this is definitely worth a read!).
My screen goes bright before unlocking / after locking?
It's a known issue when using autobrightness. There's no fix for this at the moment.
My GPS takes ages to get a lock, how can I fix it?
Try the latest version available of the Google Specific No-SSL AGPS patch by @crypted. Unpack the gps.conf file and copy it into /system/etc/ using a root file explorer (set permissions to rw-r--r--). Optionally, you can add ro.ril.def.agps.mode = 1 to build.prop (find it in /system folder) but only if you're still having problems after applying the patch.
And, in case you're wondering, the answer is no: this patch won't be integrated into the ROM, so don't ask ... or will it?
Edit: that damn Tony added it to T-Build 3, so this is no longer necessary (unless he decides to drop it hehe)
Hardware Search key is not working!
Go to Settings > System > Hardware keys and make sure that Enable custom actions is checked. Also, change Search key action to In-app Search.
Spoiler post
Well the title says it all
Spoiler nr1. here is a screenshot of battery life with this rom and KK121...
Yeah im already curious...........tout de meilleur frère :laugh:
Waiting for upload to finish....merci
rmrajm1 said:
Yeah im already curious...........tout de meilleur frère :laugh:
Waiting for upload to finish....merci
Click to expand...
Click to collapse
Already finished, tony has great upload speed hehe
Loving the structure and text of the thread, though, same with the pictures
Sent from my LG-P990 using xda premium
Can:t w8!! Good job guys!!
Sent from my LG-P990 using xda premium
Oleeeeee
Gesendet von meinem LG-P990 mit Tapatalk 2
Thanks alot , well done .. will be testing it in moments
Congrats for the release tonyp. I've been with your test builds since I found them so I'm waiting eagerly to try this final build.
Thanks for the great work!
great job done.....I am thrilled to try a CM ROM....will report a feedback....
I am sure it will rock
CONGRATS and THANKS for the hard work.
Congrats downloading it
Sent from my LG-P990 using xda premium
This sounds great. Thank you for the sacrifices you've made a big investment in this old phone that can still be done to compete with the newer devices.:thumbup::beer:
Sent from my LG-P990 using Tapatalk 2
tonyp congratulations.
Thanks for your hard work
Sent from my LG-P990 using xda app-developers app
Yeah... downloading... :victory:
I found the easter egg.. :laugh::good:
Subscribed and ready for fishslapping... xD
Downloading and flashing too.
Thank you tonyp!
Sailfish OS for Nexus 4
The porting effort is now continued by community: http://forum.xda-developers.com/nexus-4/development/rom-sailfish-os-community-port-t2969823
{
"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"
}
This is Jolla's port of Sailfish OS for the Nexus 4 (check full address in post #3)
It features a gesture-based user interface with a unique design and ease-of-use in mind.
For more information about Sailfish OS please head over to sailfishos.org.
This is not an Android ROM, this is a different base of an operating system called Linux, running the GNU C library (glibc).
It only uses parts of Android for hardware enabling (drivers).
Special Thanks to the Nexus 4 porters, carepack who took over as community's release engineer, MultiROM author Tassadar, Jolla sailors especially MSameer for camera experiments, early porters Stskeeps, lbt, thp, alterego, faenil, LEDs spiiroin, sensors lpotter, USB phdeswer, the HADK team, the Mer Project, the Nemo Project and all the fine people over at #sailfishos-porters
Release Notes:
This release is based on Sailfish OS 1.0.8.19 (Tahkalampi).
The Nexus 4 port is considered to be of beta quality.
Though depending on your usage it might be stable enough for daily use.
Download & installation instructions:
* Install adb and fastboot
a. Debian/Ubuntu: apt-get install android-tools-adb android-tools-fastboot
b. Fedora: yum install android-tools
c. Mac OS X: Install Homebrew from http://brew.sh/, then: brew install android-platform-tools
d. Windows: See http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro for instructions
MultiROM ≥v28 ability is in the image. See options of how to layout your MultiROM in #2 post below.
Alternatively, just have it as your primary ROM:
* Install Android 4.2.2 (JDQ39) to your Nexus 4
a. Instructions here: https://developers.google.com/android/nexus/images#instructions
b. Download links can be found here: https://developers.google.com/android/nexus/images#occamjdq39
* Download CyanogenMod 10.1.3 for your Nexus 4
a. Perform Factory Reset and wipe contents of the /data/ partition in case of leftovers from previous ROMs
b. The file you want to download is cm-10.1.3-mako.zip
c. Download links can be found here: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* Download the Sailfish OS for Android image for "mako"
a. The file you want to download is http://releases.sailfishos.org/sfa-ea/sailfishos-mako-release-1.0.8.19-EA4.zip
b. Another flavour filled with demo content: http://releases.sailfishos.org/sfa-ea/sailfishos-mako-release-1.0.8.19-EA4-demo-content.zip
* Install CyanogenMod 10.1.3 on your Nexus 4
a. Follow the instructions at: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* After flashing the "cm-10.1.3-mako.zip" file, flash the Sailfish OS .zip file in the same way ("on top of it")
* Reboot bootloader, Sailfish OS should boot and be visible
We recommend reading through http://jolla.com/guide/ -- some parts may not apply to Nexus 4
HW Support status:
(Look for Nexus 4 row): https://wiki.merproject.org/wiki/Adaptations/libhybris
Bug reports, if internet search refuses to help:
First search XDA for keywords. Things like libsailfishapp have already been worked out by this amazing community
Software-related bugs (Sailfish OS): first search http://together.jolla.com . Tag your questions with "community-build"
Hardware-related problems: at the Nemo Project Bugzilla under Hybris-ing component
Please do not contact Jolla Care or Jolla Developer Care, as this is not the Jolla phone
Known issues:
OTA Updates do not work
The camera does not fully work
Android app support is not available (unlike in Jolla phone): please ask about the status for open-source Dalvik runtime framework on #sailfishos-porters on irc.freenode.net and also check this XDA Thread
All remaining: In Bugzilla
Check changelog in #2 post.
Last Updated 2014-12-11
Changelog:
Read Sailfish OS release notes:
https://together.jolla.com/question...in-upgrade-to-software-version-11038-uitukka/
https://together.jolla.com/question/50175/release-notes-software-version-10819-tahkalampi/
Release notes/Known issues in EA4:
* EXPERIMENTAL: Jolla Camera
** Viewfinder stream freezes after ~20secs so be quick to take a photo
** Video recording is not available
* EXPERIMENTAL: orientation sensor works (no PS or ALS)
** was stable during tests, but we'd ask community to attempt making HADK hybris-11.0 port of mako instead, for hopes of better sensors integration
* LED notifications work
* Devicelock including Allow untrusted software
* MultiROM support (min. v28) New to MultiROM? Read here.
** you must have Android 4.2 and cm10.1 as your primary ROM
** Instructions: http://forum.xda-developers.com/nexus-4/orig-development/mod-multirom-v24-t2472295
** two alternatives for hackers:
*** 1. you can still have Android 4.4 -based secondary ROMs, provided you inject required firmwares (check MultiROM threads)
*** 2. you can have Android 4.4 as primary, flash (physically into phone's partition) modem image from 4.2 (0.84 tested OK), and still see things working in SF and CM (tested). It is not yet supported to inject radio.img for SailfishOS only (via MultiROM menu button)
* MultiROM's awesome side-effect fix - ability to power-off the device (thanks to isolated primary ROM)
* Once USB cable plugged, it gets assigned a DHCP address by an internal phone's DHCP server
* Available USB modes: Developer Mode, Charging; untested: Tethering, Mass Storage, PC Connection
Release notes/Known issues in EA3:
* EXPERIMENTAL: Jolla Store is now available, you'll need to register with your Jolla Account
** NOTE: Booting Nexus 4 with SIM first, and then removing SIM (or vice versa) may cause Jolla Store to see it as two different devices and cause potential breakage. Please stick to either SIM available or not when running Sailfish OS on Nexus 4.
** There may be a bug with oFono RIL support that makes it not report IMEI value causing this and will be sorted out in a later update.
** DISCLAIMER: Using Jolla Store with Jolla Account might break applications on your other devices, use it at your own risk!
** Android support is not available from the Store, even if you can see Android apps listed (those will be removed eventually from store view)
** This functionality means that image comes with only minimal set of pre-installed apps. Use Store to download the ones you need.
* The backlight is dark during first launch, but can be fix by switching the currently-not-working ambient light sensor off (uncheck Settings->System->Display->Adjust automatically)
* When display is blanked, power management sets WLAN to the lowest speed state
** Can be noticed in a SSH-over-WLAN session
** Chat notifications may arrive with a slight delay
Fixes after EA2:
* Watermark removed
* Phone-call audio volume can now be changed with the help of volume buttons
* Improved responsiveness when waking phone up with the power button
* Settings->System->Developer Mode or About Product do not freeze anymore
* Reverted to the original (non-Silica) Fingerterm
Fixes after EA1:
* Phone-calls with audio work
* Timers and alarms (with device powered on) work
* HTML5 video+audio works in Browser (tested splash on http://jolla.com )
* Update is based on Sailfish OS version 1.0.5.16
Release notes/Known issues in EA2:
* If not auto-detected from SIM, set-up mobile internet data settings via Settings->System->Mobile network->(long tap on the first toggle-item under "Mobile data" section)->(enter settings given by your operator)
Nexus4-specific known issues reported by the adopters:
* Chinese text input not working
* Localhost name is shown as Jolla
* Switching between the online and offline status in the status information setting takes very long and often doesn’t switch properly
* Google contacts which are put together with different information, are now split up into several contacts in Sailfish
* The battery display seems to be a bit buggy because it loses about 15% from one second to another
* The calendar overview when filled with events seems to be a bit laggy
* The email push is not working correctly, I do not receive any emails until I push the refresh button
* Splitting words in the German translation: e.g. in the open apps on the home screen it says: "Kurzzeitmesse" and in the next line the missing "r"
* NOTE: all other Sailfish OS issues have already been reported on TJC - http://together.jolla.com - and many of them were fixed in this 1.0.5.16 release
Release notes/Known Issues in EA1:
* There has been no throughout testing of telephony related functionality (roaming, airplane mode, etc) and any use of this functionality is at your own risk
* ALS and PS Sensors, Reset device, Bluetooth, USB MTP, Bluetooth, WLAN hotspot, Camera video recording, and video playback is not supported
* The image SW is not currently upgradeable, nor is any typically licensed multimedia codecs (MP3, etc), HERE maps, Android application compatibility layer, or word prediction for virtual keyboard preinstalled
* This image does not include any typically licensed multimedia codecs (MP3, etc), HERE maps, Android application compatibility layer, Microsoft Exchange support, or word prediction for virtual keyboard preinstalled
* It is not possible to double-tap to wake up the device
* FPS drop while scrolling in homescreen due to non-batching when rendering of application icon grid
* Icons/graphics appear unproportionally small in browser toolbar, time select widget, and Settings favourite icons
For even more curious ones: there has been a huge community porting effort to numerous devices, news and photos can be found here: http://forum.xda-developers.com/showpost.php?p=54302138&postcount=2
Jolla's relnotes:
Dear early adopter of Sailfish OS for Android devices. This is important - read this whole mail through and follow all steps exactly as written.
IMPORTANT: If you choose to publish this mail through blogs, news sites, forums, or others, quote it as-is and in complete form ONLY, or people's devices may be at risk.
We're happy to publish the fourth Early Adopter Release of Sailfish OS (1.0.8.19) for Nexus 4 (mako) to you.
We have also released the EA2 version of the Sailfish OS Hardware Adaptation Development Kit (HADK), as per earlier email.
This installation image is for early adopters only, meaning we know that some things are not functional or perhaps even broken -- please see the release notes below. We are excited to get all of you properly included in the early stages of the project. Do note that this Sailfish OS image is strictly for personal and non-commercial usage only.
We've prepared a 'demo' version of the image which contains the kind of preinstalled 'marketing' content and the core apps used for demonstrations - this helps you quickly get a feel for all the interactions that are avalable on a device that has been used for a while but isn't really what you want for personal use. You can however cleanly remove the demo content.
We want to build a community around Sailfish OS for Android devices that is based on mutual trust and respect for what we are all doing. Hence -- we ask that whenever you do screenshots, videos, forum or blog posts (and we're happy if you do!) or the like, you emphasise that this is work-in-progress and not a productised release. It is important for Jolla that correct expectations are set for those who might be users of the final product -- and that they understand what they see is not a released product. If you do demo videos, take advantage of our new 'demo content' image (check availability for your device) that has pre-set contacts/imagery/messages/etc to show full functionality of Sailfish OS.
WARNING: Modifying or replacing your device’s software may void your device’s warranty, lead to data loss, hearing loss, hair loss, financial loss, privacy loss, security breaches, or other damage, and therefore must be done entirely at your own risk. No one affiliated with this project is responsible for your actions but yourself. Good luck.
NOTE: You will lose your on-device data (including /sdcard), so make a proper backup and make sure to copy that backup to your PC.*
NOTE: Make sure to read all the release notes below. Please DO NOT contact Jolla Care nor Developer Care for any issues encountered with this Early Adopters build, instead use the following communication channels:
We will all meet in #sailfishos-porters (note, new location) on irc.freenode.net and please use us (thp, alterego, Stskeeps, lbt, sledges) to work together, report any bugs, graphical glitches or missing functionality that you find, which are not included in the release notes above. You can also find the hardware adaptation source code at http://github.com/mer-hybris .
You are also welcome to participate in threads at http://forum.xda-developers.com/nexus-4/general about Nexus 4 and Sailfish OS as well as for more general Sailfish OS topics at http://forum.xda-developers.com/jolla-sailfish/general
First
Is the SailfishOS 1.0.8.19 is the newest one?
thlinh130295 said:
First
Is the SailfishOS 1.0.8.19 is the newest one?
Click to expand...
Click to collapse
Yes it is, update9 is out in September
Im on the way to flash stock 4.2.2 and downloading cm + EA4, will report again
---------- Post added at 06:59 PM ---------- Previous post was at 06:56 PM ----------
one more question, do it need to use MultiRom? i use TWRP/CWM instead, it's ok?
thlinh130295 said:
Im on the way to flash stock 4.2.2 and downloading cm + EA4, will report again
---------- Post added at 06:59 PM ---------- Previous post was at 06:56 PM ----------
one more question, do it need to use MultiRom? i use TWRP/CWM instead, it's ok?
Click to expand...
Click to collapse
multirom enables you to have multiple ROMs and select them at boot
So can I flash cm10.1.3 then the E4 thru multirom and make this as a secondary ROM and expect it to boot up? I tried with E3 and it stayed at the Google boot screen. Or do I have to flash 4.2.2 then cm10.1.3 then E4 to get it to boot? It's insanely confusing. Lil help would be nice.
And can I use this http://forum.xda-developers.com/nexus-4/development/Rome android as my 4.2.2 base before flashing cm10.1.3?
Nix all this. I flashed cm10.1.3 then the EA4. It loaded fine but the problem I'm having is no wifi...do I need to set get a 4.2.2 radio IMG to set for it to pic up wifi? I have a mobile connection. Jus no wifi.
x.0ni.x said:
So can I flash cm10.1.3 then the E4 thru multirom and make this as a secondary ROM and expect it to boot up? I tried with E3 and it stayed at the Google boot screen. Or do I have to flash 4.2.2 then cm10.1.3 then E4 to get it to boot? It's insanely confusing. Lil help would be nice.
And can I use this http://forum.xda-developers.com/nexus-4/development/Rome android as my 4.2.2 base before flashing cm10.1.3?
Nix all this. I flashed cm10.1.3 then the EA4. It loaded fine but the problem I'm having is no wifi...do I need to set get a 4.2.2 radio IMG to set for it to pic up wifi? I have a mobile connection. Jus no wifi.
Click to expand...
Click to collapse
what kernel you're using? You have to flash the modem of android 4.2.2 ak 0.84 or google factory 4.2.2 image.
flashable zip of modem:
http://forum.xda-developers.com/nexus-4/general/ref-mako-modem-collection-t2087227
google factory image:
https://dl.google.com/dl/android/aosp/occam-jdq39-factory-345dc199.tgz
and a lttle help from first post:
Download & installation instructions:
* Install adb and fastboot
a. Debian/Ubuntu: apt-get install android-tools-adb android-tools-fastboot
b. Fedora: yum install android-tools
c. Mac OS X: Install Homebrew from http://brew.sh/, then: brew install android-platform-tools
d. Windows: See http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro for instructions
* Install Android 4.2.2 (JDQ39) to your Nexus 4
a. Instructions here: https://developers.google.com/androi...s#instructions
b. Download links can be found here: https://developers.google.com/androi...ges#occamjdq39
* Download CyanogenMod 10.1.3 for your Nexus 4
a. Perform Factory Reset and wipe contents of the /data/ partition in case of leftovers from previous ROMs
b. The file you want to download is cm-10.1.3-mako.zip
c. Download links can be found here: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* Download the Sailfish OS for Android image for "mako"
a. The file you want to download is http://releases.sailfishos.org/sfa-e...0.8.19-EA4.zip
b. Another flavour filled with demo content: http://releases.sailfishos.org/sfa-e...mo-content.zip
MultiROM ≥v28 ability is in the image. New to MultiROM? Read here. Check for more DIY alternatives how to layout your MultiROM in #2 post below.
Click to expand...
Click to collapse
x.0ni.x said:
So can I flash cm10.1.3 then the E4 thru multirom and make this as a secondary ROM and expect it to boot up? I tried with E3 and it stayed at the Google boot screen. Or do I have to flash 4.2.2 then cm10.1.3 then E4 to get it to boot? It's insanely confusing. Lil help would be nice.
And can I use this http://forum.xda-developers.com/nexus-4/development/Rome android as my 4.2.2 base before flashing cm10.1.3?
Nix all this. I flashed cm10.1.3 then the EA4. It loaded fine but the problem I'm having is no wifi...do I need to set get a 4.2.2 radio IMG to set for it to pic up wifi? I have a mobile connection. Jus no wifi.
Click to expand...
Click to collapse
Yes, 4.2.2 radio IMG needs flashing. But have no fear, we tested: primary CM11 still fully works with that, including 3G, so I don't even know what are the so-important radio.img differences there
carepack said:
what kernel you're using? You have to flash the modem of android 4.2.2 ak 0.84 or google factory 4.2.2 image.
flashable zip of modem:
http://forum.xda-developers.com/nexus-4/general/ref-mako-modem-collection-t2087227
google factory image:
https://dl.google.com/dl/android/aosp/occam-jdq39-factory-345dc199.tgz
and a lttle help from first post:
Click to expand...
Click to collapse
Awesome!! Thank you!! Found the radio in zip form. Fixing to flash in a few minutes!! I'll get bk to you shortly to let u know if this works! It's coming along tho. At least the camera is working and suck on this OS. Can't wait to see what the next update entails!!
x.0ni.x said:
Awesome!! Thank you!! Found the radio in zip form. Fixing to flash in a few minutes!! I'll get bk to you shortly to let u know if this works! It's coming along tho. At least the camera is working and suck on this OS. Can't wait to see what the next update entails!!
Click to expand...
Click to collapse
Read first post
sledges said:
Yes, 4.2.2 radio IMG needs flashing. But have no fear, we tested: primary CM11 still fully works with that, including 3G, so I don't even know what are the so-important radio.img differences there
Click to expand...
Click to collapse
Flashed radio image zip fill over sailfish os still no wifi connection grrrr so frustrating. I want this to work but lost now
---------- Post added at 11:36 PM ---------- Previous post was at 11:35 PM ----------
carepack said:
Read first post
Click to expand...
Click to collapse
Read it over and over tyvm
x.0ni.x said:
Flashed radio image zip fill over sailfish os still no wifi connection grrrr so frustrating. I want this to work but lost now
Click to expand...
Click to collapse
Which radio.img did you flash? Try another one, too. If you tried 0.84, then try 0.54 instead, or vice-versa. We did not test any others (and newer than 0.84 won't work)
sledges said:
Which radio.img did you flash? Try another one, too. If you tried 0.84, then try 0.54 instead, or vice-versa. We did not test any others (and newer than 0.84 won't work)
Click to expand...
Click to collapse
Tried .83. I'll download the other 2 now. Thanks again.
x.0ni.x said:
Tried .83. I'll download the other 2 now. Thanks again.
Click to expand...
Click to collapse
If you're still unlucky, could you give more info as to how exactly does the WLAN not work?
Do you enable it via Settings->WLAN (click on glowing bulb switch), then use pulley menu to "Connect to Internet" ?
sledges said:
If you're still unlucky, could you give more info as to how exactly does the WLAN not work?
Do you enable it via Settings->WLAN (click on glowing bulb switch), then use pulley menu to "Connect to Internet" ?
Click to expand...
Click to collapse
Flashed 0.54,0.83, & 0.84. Same thing for all 3. And yes that's how I'm TRYING to enable it. But it just says on that screen where u pull it down to "connect to the Internet" "unable to connect to internet. Please restart your phone". I even reflashed the ROM with all 3 radios and still nothing. I as well hit the lil "lightbulb"wifi switch in the row of like Bluetooth, mobile connection, etc. It comes on but I go to the WLAN connection to get wifi going nothing still. Same message.
I flashed 0.84 radio and Wi-Fi don't work too.
Kubino said:
I flashed 0.84 radio and Wi-Fi don't work too.
Click to expand...
Click to collapse
which kernel you're on?
try this one:
http://d-h.st/users/hellsgod/?fld_id=28949#files
If you have as first rom an cm rom then take the file with cm in the name
If you're on aosp android use the one without it. In my constellation it works quite right.
So the steps I've done:
1. I had an android AOSP rom as primary.
2. I've downloaded the kernel without cm in the name. Correct kernel is needed with kexec patch. Is included in the files
3. downloaded sfosEA4 and cm10.1 and radio 0.84
4. In android I've downloaded multirom manager from play store.
so this were my requirements. now the todo:
1. went into recovery and flash the kernel
2. went back into android / multirom manager and do the installation process
3. after some time you'll be back in android and installation is finished
4. reboot into recovery. flash modem 0.84
5. go back to android and look if everything is working
6. then back to recovery again Go -> Advanced -> add rom -> sailfish
7. then you can select 2 zips. first one is cm10.1 and second is sailfish
8. install
9. after that you'll be able to boot sailfish too. everything should be fine.
carepack said:
which kernel you're on?
try this one:
http://d-h.st/users/hellsgod/?fld_id=28949#files
If you have as first rom an cm rom then take the file with cm in the name
If you're on aosp android use the one without it. In my constellation it works quite right.
So the steps I've done:
1. I had an android AOSP rom as primary.
2. I've downloaded the kernel without cm in the name. Correct kernel is needed with kexec patch. Is included in the files
3. downloaded sfosEA4 and cm10.1 and radio 0.84
4. In android I've downloaded multirom manager from play store.
so this were my requirements. now the todo:
1. went into recovery and flash the kernel
2. went back into android / multirom manager and do the installation process
3. after some time you'll be back in android and installation is finished
4. reboot into recovery. flash modem 0.84
5. go back to android and look if everything is working
6. then back to recovery again Go -> Advanced -> add rom -> sailfish
7. then you can select 2 zips. first one is cm10.1 and second is sailfish
8. install
9. after that you'll be able to boot sailfish too. everything should be fine.
Click to expand...
Click to collapse
I have Paranoid Android 4.5 beta 2 as my primary ROM with the kernel you have as well. Also have Miui V5 installed with hellscore B47 as the kernel. I knew this in advanced as I figured Jolle was going to possibly release an update because multiROM had made it possible to finally flash it. Did all the steps provided above to my own knowledge. I think I'll delete the sailfish and start fresh. Hopefully that will work. If not may just be a bug that will be solved I'm sure. As these builds are only EXPERIMENTAL not even Alpha yet. Major bugs are to be expected. So no worries. I just really like the design of this OS outside of android.
EDIT. Are you saying to flash the radio over my primary ROM (PA 4.5 BETA 2 or the sailfish OS)? I flashed over the radio over the sailfish OS not primary. Just to be completely clear here.
Discussion Thread for AOSP Nougat ROM (SanthoshM)
Hi all,
See the main development thread here
Please consult the FAQ/Issues/Changelog list below before posting, some of your problems might have been solved already!
Since the main thread for the still-WIP Nougat 7.0 ROM by @santhoshm was getting very cluttered with the same questions and answers, making new updates by the OP difficult to find, I thought we could use this thread to discuss bugs, issues anyone is having installing the ROM and configuring apps, and answering general frequent questions without clogging the main thread.
This gets updated at least once per day
Useful Utils
-----------------------------------------------------------------
Nexus 5 Google soundkit and Pixel Launcher Flashable ZIPs by @edwaine (link to APK by @occtec)
If you're tired of the AOSP sounds and/or want the leaked Pixel Launcher as a flashable ZIP, see this post.
Debloater Scripts by @androcraze
Updated link to separate thread: you're now welcome to discuss any issues or feedback with the debloater scripts or DeltaDroid's GApps packages over there.
Selection of flashable ZIPs that remove some/all of the preinstalled (old) AOSP apps from the ROM completely. You can choose to remove them all, or keep some, plus we recommend great FOSS alternative apps for the Google equivalents. Choose from Maximum, Medium or Minimum debloating.
FAQs
-----------------------------------------------------------------
Send a "thanks" to @androcraze for his additional collation of FAQs and notes integrated into this post!
Please read this section before posting a question or bug, it might already be answered here!
Changelogs for FAQs
Code:
[LIST]
18 September 2016
[*] New build added
8 September 2016
[*] Added YouTube fix
[*] New links to debloat script
[*] New build available
7 September 12PM
[*] Added fix for phone crashing
3 September 3pm SAST
[*] New build (see changelog)
1 September 12PM SAST
[*] Added new build info
30 August 5pm SAST
[*] Added potential fix to green screen on video recording
30 August 12am SAST
[*]Added info on battery drain solution
[*]Added info on root access
29 Aug 12am SAST
[*] Added "debug-only private cache fix
[*] Added green-screen flicker issue
[*] MultiROM fixes!
28 Aug 12am SAST
[*] Modified FAQ with the new build
[*]Added tip on keeping Night mode active
27 Aug 7pm SAST
[*] Fixed broken link to green line fix on video
27 Aug 12PM SAST
[*] Improved GApps install instruction (See Installation FAQ)
[*]Added solution to TimeService issue (See Usage FAQ)
[*]Added solution to Boot animation missing (See Installation FAQ)
[*]Added possible solution for green line (see Apps FAQ)
[/LIST]
Installation FAQ
Q: Which recovery should I use for this ROM?
A: TWRP 3.0.1 or 3.0.2 is required.
Q: Does Busybox work?
A: Yes, check here.
Q: How do I get root?
A: As you would normally - download this SuperSU ZIP (latest 2.77 beta works fine) and copy it to your device storage. Reboot into TWRP and flash the ZIP, then reboot the device. If the boot loops once or twice, that's normal. Once it's done, you can confirm by checking for the "SuperSU" app in your app tray.
Q: Which GApps to use?
A: Check out pico, nano or micro GApps on the Open GApps page. Some have had luck with Mini but this varies by build.
Q: Can I use MultiROM to install this ROM?
A: Update 29 Aug : MultiROM fixes here Courtesy of @blade
Q: Procedure to install ROM with GApps
A: Note: Latest ROM build allows flashing ROM + GApps in one queue without crashes
(For older builds) A: Don't flash the ROM together with GApps in the same ZIP queue because this will cause the Installation Wizard to run on first boot. Due to Google Play permissions errors the Wizard will keep crashing and you won't be able to bypass this. Solution:
1. Enter TWRP, wipe as needed, install the ROM via TWRP
2. Reboot the phone to Android (configure WiFi and APN info).
3. Reboot back to recovery
4. Install GApps via TWRP
5. Boot to System (Yes, you'll probably get Play Services "FC" messages until you perform #6, below)
6. Immediately toggle application permissions to "ON" under:
Settings -> Apps -> ... -> System show
For:
- Google Contacts Sync
- Google Play Services
- Google Play Store
7. Reboot the phone
8. Add your Google Account via "Settings -> Accounts -> Add account -> Google"
9. Verify that Contacts are synced and Play Services is functional.
Q: Why does Settings > Backup and restore shows "debug-only private cache" instead of my Google account?
A: There's a fix (Tested as working!) that you can try here
Q: After flashing TWRP says "No OS Installed?" Note: This has been fixed in the latest build)
A: Ignore this message. If the ROM flash indicated as being successful, you can swipe to reboot and the OS should boot.
Q: After flashing the ROM I've lost TWRP, what gives?
A: Since this was a stock AOSP image it includes stock recovery. Do this to get TWRP back;
Enable developer options on your device by pressing the build number 7 times on Settings > About Phone
Enable USB debugging in developer options
Connect your device to your PC and issue
Code:
adb reboot-bootloader
from wherever your ADB is installed
Place the TWRP image in the ADB folder.
Your phone should restart to the fastboot interface. Now issue
Code:
fastboot flash recovery <twrp.img>
where <twrp.img> is the name of the TWRP file
When that's done, issue
Code:
fastboot reboot-bootloader
and choose "Enter recovery" to go into your TWRP
Ensure TWRP performs the one-time step of setting itself to read-write permissions, by else it'll disappear again on next boot.
Newer builds are being reported to preserve TWRP on reflash.
Apps FAQ
Q: My Google Play Store / Google Play Services / Apps keep crashing?
A: This is a permissions issue. Go to System Settings > Apps (top right menu button) > Show System
Set the following to resolve most crashes:
Google Contacts sync > Contacts permission
Google play services > all permissions
Q: My contacts aren't syncing?
A: Give the contacts app contacts permission and try Settings > Accounts > Google > Contacts (uncheck and recheck)
If this doesn't work, uninstall the GApps contacts APK, and install this Google Contacts APK as an update to the system one. Perform the step above and contacts should sync.
Q: What if I want to use the setup wizard to copy apps, accounts and data after install?
A: Install the ROM and GApps as advised in the Installation section, once you've set up everything and permissions etc. do a factory reset. This should fix it (thanks @devilsadidas for the tip).
Q: Where is the System Tuner UI?
A: Enable Developer Options (under "About Phone", tap "Build Number" seven times), then long-press the settings icon in the notification shade/bar.
Q: How do I get rid of the green screen flickering in video recording?
A: This is a known issue (See Known Issues). Update - @nisby reports (confirmed) that using Footej Camera solves the problem. If you per sé want to us Google Camera or the AOSP Camera, @chrisk44 reports the 25/08 build doesn't have that problem.
Q: My YouTube Videos don't play or throw an error
A: This can be fixed by flashing the 16/09 build.
Usage FAQ
Q: My date and time keeps resetting on successive boots?
A: Solution is to install the Qualcomm TimeService app (a proprietary application)
- the 6.0.1 version (tested successfully with 7.0) is available HERE
Q: Does this build support Vulcan?
A: No. Vulcan does not provide support the Nexus 5.
Q: Does doze work in this build?
A: Yes. You do not have to enable anything; it is active by default.
Q: Can I use this ROM with Android Pay?
A: No. Only approved factory ROMs from Google can use Android Pay. If you want Android Pay on the Nexus 5, install a Marshmallow factory image.
Q: Where can I get the Nougat bootanimation?
A: Try Post #1 in this Boot Animation Collection. Or flash 16/09 build.
Q: If you can't install apps from Play Store: (error code DF-DLA-15)
A: Go to Settings/Apps/Google Play Services/Storage/Manage space/Clear all data.
Then go back to:
Settings/Apps/Google Play Services/Permissions and turn on all permissions (thanks to @BazingaOG for this tip)
Q: My battery charges slowly. Now what?
A: This is a known issue. See "Known Issues" below and check the Changelog below for any updates on this. (Thanks to @olivercervera )
Q: How is battery life with Nougat on the Nexus 5?
A: It should be comparable to Marshmallow. If you're having battery drain issues and are rooted, try this solution.
Q: Why is the font scaling on the date/time quick settings pulldown weird?
A: Known issue. Switch "Display size" (NOT "Font size") in Settings to "Small". (Thanks @Nick80835 for the tip)
Q: Where can I find your build tree?
A: It will be posted once the ROM is stable.
Q: Can you add new features?
A: The goal of this ROM is to get a clean build under AOSP. "Features" aren't a priority.
Q: Night mode won't stay enabled if I try to toggle it?
A: Touch the "on" label on the left to turn it on, NOT the toggle switch on the right (thanks @smartboy0668 for the tip)
Known Issues
As of 8 September:
YouTube doesn't play for some. 16/09 build apparently fixes this.
Some users report crashes, blank-screening in-call and permissions issues with Google Play Phone app despite setting permissions. Confirmed solution here. (Thanks @DVDandroid and @jokerclown)
Settings > Backup shows "debug-only private cache" instead of Google account (Solution under Installation FAQ) Fixed in 08/09 build
Video green-screen flickering (discussed here) - App fix here . Use 25/08 build for working Google Camera. (Thanks to @chrisk44 for the tip)
Carriers such as Sprint have no signal (confirmed by @famewolf)
Changelogs for ROM
16 September
Changelog :
Updated to android 7.0.0_r6 (NRD90U)
Should fix youtube issues for some users
Security vulnerability CVE-2016-2059 patched (as reported by a user)
AOSP nougat bootanimation added
Other non AOSP features ( UItuner features & others) continue to remain
Click to expand...
Click to collapse
8 Sept @ 11PM SAST
Changelogs :
Updated to android 7.0.0_r4 (NRD90S)
September security patch
"debug-only private cache" in settings-backup should be fixed now (thanks @Rapper_skull for the patch )
About phone will now reflect Nexus 5 instead of "AOSP on hammerhead"
Other non AOSP features ( UItuner features & others) continue to remain
Click to expand...
Click to collapse
3 Sept @ 3pm
Changelogs : (03/09/2016)
Implemented webview patch based on @Rapper_skull patch and discussion with @osm0sis
(device boots now even when there is no gapps flashed. I haven't tested flashing with gapps nor tested if the webview implementation works correctly ! Would be nice if someone does)
Switched from eng build to userdebug build
Added support for gesture swiping in keyboard.
Enable/disable toggle to hide brightness in quick settings is now available and is there in systemui tuner menu ( It's just a aosp feature and was just hidden and i have unhided it)
Click to expand...
Click to collapse
1 Sept @ 12pm
Fix settings FC on boot
Disable data roaming by default
Advanced reboot feature ( reboot is a must needed thing and hence )
Previous hidden systemui tuner features continue to remain
Click to expand...
Click to collapse
27 August @11pm
Released a new build (27/08/2016)
Nothing much, just goodies and improvements. Previous hidden systemui tuner features continue to remain
Goodies :
* Double tap on statusbar to sleep
Improvements :
* Gapps permission grant patch included in the OS
* Fix the "No OS installed" message when you try to reboot after flashing the ROM via twrp
Click to expand...
Click to collapse
25 August @ 7pm
Issues fixed :
* Camera pictures not getting saved ( Have checked video recording too )
* Enabled the power modes doze flag
Additional goodies :
Both these will be available in systemui tuner
* Enabled night mode ( i am loving it )
* Nav bar customization
Download link available in OP
Click to expand...
Click to collapse
I flashed this ROM today and installed OpenGApps Aroma package. Then after the first boot I did all the permission stuff i.e. provided all the permissions to Play Services and related apps.
But I am still unable to load up my Google Account, Play Services still Force Close on adding a account. Any Help is appreciated.
CrashOverride1995 said:
I flashed this ROM today and installed OpenGApps Aroma package. Then after the first boot I did all the permission stuff i.e. provided all the permissions to Play Services and related apps.
But I am still unable to load up my Google Account, Play Services still Force Close on adding a account. Any Help is appreciated.
Click to expand...
Click to collapse
I'm not sure if this will help, but did you flash the ROM and then GApps straight after it? That caused issues for me. I flashed the ROM, booted into it once without GApps, then rebooted to TWRP and installed GApps, which suppressed the installation screen and allowed me to add Google accounts without crashes.
CrashOverride1995 said:
I flashed this ROM today and installed OpenGApps Aroma package. Then after the first boot I did all the permission stuff i.e. provided all the permissions to Play Services and related apps.
But I am still unable to load up my Google Account, Play Services still Force Close on adding a account. Any Help is appreciated.
Click to expand...
Click to collapse
MattDN93 said:
I'm not sure if this will help, but did you flash the ROM and then GApps straight after it? That caused issues for me. I flashed the ROM, booted into it once without GApps, then rebooted to TWRP and installed GApps, which suppressed the installation screen and allowed me to add Google accounts without crashes.
Click to expand...
Click to collapse
Exactly what @MattDN93 says, also make sure you give all Google Apps which you have installed all needed permissions, just to be sure that they all work as they should. I had the same problem but after checking and allowing the needed permissions everything worked just fine. I use the the OpenGapps Micro Package, you might want to try a clean flash with the suggested flashing order (First the ROM, boot up and then flashing Gapps after) and try the Micro Package, maybe that will work better for you. :good:
Thanks for making this thread!
Could you tell me if Santosh's latest build is more stable than cdesai's or not?
Karan_Brar said:
Thanks for making this thread!
Could you tell me if Santosh's latest build is more stable than cdesai's or not?
Click to expand...
Click to collapse
No problem! From what I can see Santosh was updating his build to fix the camera saving issues that CDesai's build already had sorted. However, check the changelog above - Santosh has added Night mode and fixes for Doze, so theoretically his build should be as stable as CDesai with extra features. I haven't flashed the latest one yet but I will report back here (or you could, whoever flashes it first ).
How do I get the setupwizard after i install the gapps? I need it so it can sync all my app data and settings
Thank you for all your work
gabel160 said:
How do I get the setupwizard after i install the gapps? I need it so it can sync all my app data and settings
Thank you for all your work
Click to expand...
Click to collapse
A factory data reset should do it
Sent from my AOSP on HammerHead using Tapatalk
I'm running the latest build of SanthoshM and it's very stable at the moment but I have a issue on something
I can enable battery percentage in system UI tuner but sometimes battery percentage disapears and I have to enable it back in system UI tuner. Last time, it disapeared after a reboot. Other persons who have this issue?
Great, thanks for this thread, It may be useful to most. people.
@MattDN93, you may want to add the only known issue so far: slow battery charging, @ 0.75A, measured with a tester.
olivercervera said:
Great, thanks for this thread, It may be useful to most. people.
@MattDN93, you may want to add the only known issue so far: slow battery charging, @ 0.75A, measured with a tester.
Click to expand...
Click to collapse
No prob I've PMed Santhosh to add this thread to the OP perhaps so people will find it easier. Thanks for the heads up on that, will add to post now.
It loses permission if I factory reset, so the problem persists
gabel160 said:
It loses permission if I factory reset, so the problem persists
Click to expand...
Click to collapse
Try to wipe all and do a fresh install. It ran setup wizard for me first try. Using pico gapps
Sent from my AOSP on HammerHead using Tapatalk
Is it just me or it happens with everyone that Google Now on Tap FCs the Google App??
Sent from my Nexus 5 using Tapatalk
devilsadidas said:
Try to wipe all and do a fresh install. It ran setup wizard for me first try. Using pico gapps
Sent from my AOSP on HammerHead using Tapatalk
Click to expand...
Click to collapse
Can you describe your whole installation process? Did you use 7.0 gapps?
I did it like this and it doesnt work:
1. Install the ROM
2. Reboot into ROM
3. Reflash recovery and install 7.0 micro gapps
4. reboot ROM and enable all permissions for Contact Sync, Google Framework service , Google Play Store , Google Play services and Setup Wizard
5. Factory reset in Twrp
and then I still get the problem with the wizard that the Google play services force close.
CrashOverride1995 said:
Is it just me or it happens with everyone that Google Now on Tap FCs the Google App??
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Me either.
someone knows that the process is called VARIOUS spending 41 % of battery? spends more battery than the screen
{
"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"
}
I have little bug...after enabling bluetooth for my Moto360, the Bluetooth icon is doubled on the status bar. If I disable bluetooth, one icon is disappearing but the other is still there
gabel160 said:
Can you describe your whole installation process? Did you use 7.0 gapps?
I did it like this and it doesnt work:
1. Install the ROM
2. Reboot into ROM
3. Reflash recovery and install 7.0 micro gapps
4. reboot ROM and enable all permissions for Contact Sync, Google Framework service , Google Play Store , Google Play services and Setup Wizard
5. Factory reset in Twrp
and then I still get the problem with the wizard that the Google play services force close.
Click to expand...
Click to collapse
Actually your right, i did not go through the setup wizard and it wouldn't go through it after the data reset either. i guess for that you may just have to wait till more is ironed out. sorry to mislead you
XOSXOS Chameleon ported from infinix Hot 4
{
"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:
Code:
I'm not responsible if your device gain the ability to fly or
became very cool & awesome after flashing this rom!
You're flashing this at your own risk.
After countless time spent on porting this rom, I present to you the beautiful XOS rom !
What is working?
- Display
- Sound
- WiFi
- Bluetooth
- GPS
- Camera (Primary & Secondary)
- Storage (SD card & internal storage)
- Ril
- FM radio
- Xtheme
- All x apps
- Root
- ... etc
- almost everything
What is not working?
- Flash light toggle in systemUI
Bugs:
- Notification LED is buggy Fixed
- No bugs in the rom.
Changelog:
Version 1:
Code:
- Based port on X557-H807A1-M-160815V57
- Added USB storage in build.prop
- Fixed screen lock password
- Removed apps inside system/vendor to reduce zip size
Version 2:
Code:
- Used better META-INF [SIZE="1"][COLOR="Gray"](Faster flashing process).[/COLOR][/SIZE]
- Used Android one 08082016 kernel.
- Changed mount point names in updater-script to Android one partition table [SIZE="1"][COLOR="gray"](Do not flash on infinix rom partition table).[/COLOR][/SIZE]
- Changed boot logo [SIZE="1"][COLOR="gray"](Used infinix Hot 4 logo)[/COLOR][/SIZE]
- Deleted some system apps to optimize rom for Android one system partition [SIZE="1"][COLOR="gray"](Deleted: Compass, Drive, Hangouts, fingerprint, Feedback, Google play music, User guide, XClub, and XShare)[/COLOR][/SIZE]
- Zipaligned apps to optimize ram.
- Replaced AOSP keyboard with Xperia keyboard by bejunk [SIZE="1"][COLOR="gray"](Keyboard has emotion prediction and skins)[/COLOR][/SIZE]
- Added apps to data/app [SIZE="1"][COLOR="gray"](Google Camera, Xposed installer, Xposed torch)[/COLOR][/SIZE]
- Added power saving tweak in build.prop
- Added low ram configuration tweak in build.prop
- Added Busybox zip.
- Fixed root and [B]added[/B] root package in rom zip [COLOR="gray"][SIZE="1"](No need to flash root after flashing the rom, it is already rooted!).[/SIZE][/COLOR]
- Fixed Notification LED and Charging LED.
- Fixed FM radio messed channels.
- Fixed Camera panorama FC when start recording.
- Fixed Gallery FC when editing a picture.
- Fixed lockscreen wallpaper doesn't change with theme.
- Fixed font not changing bug [SIZE="1"][COLOR="Gray"](report if it doesn't work for you, I'll look into it later) , (Fonts started to work for me when I done te following, [URL="http://forum.xda-developers.com/showpost.php?p=68753824&postcount=153"]check here[/URL]).[/COLOR][/SIZE]
Version 3:
Code:
- Rebased the port on firmware from Infinix Hot4 lite latest update.
- Used kernel from 20160914 Android one update.
- Used all audio libs from Hot 4 firmware instead of Hot 2 audio libs that were in pervious versions.
- Removed Hot 4 kernel logo as it shows glitches in offline charging. [SIZE="1"][COLOR="Gray"]( If you were on version 2, flash logo.bin from stock rom via sp flashtool )
[/COLOR][/SIZE]- Edited Updater-script to be flashable on both Infinix and Android one partition table. [COLOR="gray"][SIZE="1"]( To make flashing esaier for you ;) )[/SIZE][/COLOR]
- Added Google keyboard instead of AOSP keyboard [SIZE="1"][COLOR="Gray"]( For those having "keyboard not showing in setup wizard" issue )[/COLOR][/SIZE]
- Added support for missing Engineer mode *#*#3646633#*#*
- No Finger Print related settings/app on this rom.
- Status Bar is now tinted, no need for "Flat style bars" Xposed module.
- Removed build.prop tweaks.
- Fixed Google Camera, and related force closes in the app.
- Fixed GPS accurecy.
- Updated superSU and BusyBox.
Version 4:
Code:
- Rebased my port on the recent update from infinix (10-January-2017).
- Some other minor changes
- Infinix [URL="http://prtsc.ca/i/6rBcb"]changelog[/URL]
Version 5:
Code:
- Rebased on version 4
- Video bug fix by @memoo_mshm
Version 5.1:
Code:
- Rebased on version 4
- Updated vendor blobs
- Updated Boot.img zImage
- Fixed video bug
Screenshots
- Look in the screenshots tab.
Workaround for notification LED and flash light toggle: (fixed. this is not needed anymore)
- For LED you can try LED blinker notifications or Light flow with root to control LED and flash light, from playstore.
- You can also download any Torch app as an alternative for broken flash light toggle. (use xposed torch)
DownloadVersion 1:XOS Chameleon V.2.0.0Version 2:XOS Chameleon V.2.0.0 (2nd port)Version 3:XOS Chameleon V.2.0.0 (3rd port)Version 4:XOS Chameleon V.2.0.0 (4th port)Version 5 by memoo_mshm:XOS Chameleon V.2.0.0 (5th port)
UpdateVersion 5.1:XOS Chameleon V.2.0.0 (5th port - 5.1)
How to flash?
- Make sure you have Android one partition table (Flash Android one rom via SP flashtool).
- If you don't have a custom recovery, download from here (works well, recommended), or TWRP 3.0.2-1 for Hot 2 from Hovatek and flash it via SP flashtool.
- Reboot into recovery (Power off your phone, wait until it vibrates, hold power button + volume up button simultaneously)
- Wipe everything except SD card; wipe Cache, Dalvik /art Cache, Data, system. Internal memory is optional.
- Flash XOS rom, and Xposed framework then reboot. (Xposed framework is recommended for xposed torch to work with hardware buttons)
- Alternatively you can try dual boot patcher to flash rom. (SD card doesn't work when using the app with MM roms)
- If you are flashing a newer version of the rom no need to wipe anything. (wipe only in this case if you faced problems).
FAQ
Code:
[B]- Can't grant permission for an app?[/B]
Turn off all the draw over other app options.
[B]- Enable Magazine lock screen?[/B]
Go to Settings/Security choose Magazine lock screen.
[B]- Notifications not showing on lock screen?[/B]
Go to Settings/Sound & notification/Notifications choose "when device is locked" then "show all notifications content"
[B]- How to uninstall an app from launcher?[/B]
Xlauncher is a lil bit like EMUI launcher; apps present on home screen, what looks like an app drawer is just a small app to arrange apps from A-Z. So breifely uninstall app from home screen.
[B]- Status bar is not tinted on some apps? (Fixed on version 3).[/B]
This is not a port bug, XOS rom is just like that.. use flat colored bars xposed module to change it. (not needed now)
[B]- Can I use/enable USB OTG?[/B]
USB OTG is not supported by defualt in Hot 2 Android one kernel, we need kernel support for this feature to work.
[B]- How to remove fingerprint app from the app drawer? (removed on version 3)[/B]
You can't. It is inside settings.apk ; it needes to be deodexed and modified to remove it, so just ignore it.
[B]- Is flash light toggle/kernel gestures are going to be fixed?[/B]
No, it is impossible without kernel support.
[B]- I can't find a specific feature/this feature is missing?[/B]
Well, I only port the rom, I do not add features to it, if you can't find a specific feature you used to have on another rom, then simply it is not supported in XOS rom.
[B]- Night mode in camera force closes?[/B]
It is not supported, do not use it.
[B]- I found a bug, can you fix it?[/B]
Give me a logcat of the bug and for sure I'll try to fix it.. So logcat or it never happened.
[B]- When some bugs will be fixed?[/B]
Don't ask for ETA please, some bugs are hard to fix and other are unfixable.
~ Happy flashing ~
XDA:DevDB Information
XOS Chameleon, ROM for the Infinix HOT 2
Contributors
Mysteryagr, Nonta72
ROM OS Version: 6.0.x Marshmallow
ROM Firmware Required: Android one partition table
Based On: Infinix UI
Version Information
Status: Stable
Current Stable Version: 5
Stable Release Date: 2017-3-22
Created 2016-09-06
Last Updated 2017-3-22
Reversed
Reversed
This is not needed anymore!
Flashing XOS rom on Android one
This is for people who do not want to flash infinix rom, or they don't know how to, or they found it a difficult task!
Some informations:
Android one has a small system partition approximately 1.80 GB, so when you try to flash some roms it will fail because of low space.
Usually the workaround for this is flashing infinix rom via SP flash tool (select format + download) it will change your phone partition table giving you a bigger system parition.
Even though this task is very easy, I get so many messages from people complaining about bootloops, or they couldn't flash infinix rom and they soft bricked their devices.. some other flashed infinix rom via custom recovery and they wonder why XOS bootloop for them * facepalm *
Workaround for you
1- Download XOS rom
2- Unzip it
3- Delete META-INF folder.
4- Download META-INF from attachments, unzip it to rom directory)
5- Go to system/app and delete some apps to free some space, for example you can delete (Chrome, Hangouts, Youtube, & userguide.. etc)
6- Make sure that system folder size is less than 1.80 GB (1.70 or 1.60 GB just in case)
7- zip the rom back
8- Flash it, it should boot.
Notice: current bugs in the rom cannot be fixed, I won't provide further updates.
(One more reserve).
Good job bro!
Gonna share it on my blog.
Nonta72 said:
(One more reserve).
Good job bro!
Gonna share it on my blog.
Click to expand...
Click to collapse
Thanks Bro
Go ahead, the rom won't be possible without your porting method
SD
Guys i have to Ask ..
First of all thanks for your great work ..
Second : i Tried to port it before but i got the SD Card is corrupted bug >> How Did you fix "SD card is Corrupted" bug ..
Please Reply to me .. :angel:
Thanks
Mazen Yasser said:
Guys i have to Ask ..
First of all thanks for your great work ..
Second : i Tried to port it before but i got the SD Card is corrupted bug >> How Did you fix "SD card is Corrupted" bug ..
Please Reply to me .. :angel:
Thanks
Click to expand...
Click to collapse
I didn't test SD Card actually, I flashed the rom via Dual boot patcher and it breaks SD card on MM roms.
Wait for someone to confirm that it is working, if it is.. all I've done is changed the mount point in the updater-script for flashing boot.img
Edit: SD card confirmed to be working.
Which recovery should we use?
emeey100 said:
Which recovery should we use?
Click to expand...
Click to collapse
TWRP 3.0.2 recommended.
LED is working but it is buggy, and charging LED doesn't work.
Frist of all
Good work bro And thanks for that amazing rom It's very smooth
But i found 2 bugs
1- usb connection didn't work with me even usb debugging
2- it same room unable to root
I've tried everything apps and su zips also
mody oka said:
Frist of all
Good work bro And thanks for that amazing rom It's very smooth
But i found 2 bugs
1- usb connection didn't work with me even usb debugging
2- it same room unable to root
I've tried everything apps and su zips also
Click to expand...
Click to collapse
1- USB on which mode? MTP or USB storage? what windows you have?
MTP mode doesn't work on windows 10, USB storage only.
2- it doesn't seem to work, didn't find a solution yet.
why just stuck in booting?:crying:
farrasto7 said:
why just stuck in booting?:crying:
Click to expand...
Click to collapse
Because you didn't follow the instructions, are you on Android one rom?
Android one rom has small system partition
Android one system partition = 1.82 GB
XOS rom size = 1.88 GB
It will fail if you try to install it on Android one rom.
You need to flash Infinix rom first via SP flash tool, it will modify partition table and you will have bigger system partition.
And do not flash root, it either bootloop or doesn't grant permissions.
farrasto7 said:
why just stuck in booting?:crying:
Click to expand...
Click to collapse
The ROM installation takes a lot of time(abt 20min). I almost aborted it. I tot it had freezed because it stood still at 'formating system' but later continued.
The bootloop occurred when I tried rooting the ROM so don't root it yet after installation.
-Please how do we fix the led notification bug?
Toluene15 said:
The ROM installation takes a lot of time(abt 20min). I almost aborted it. I tot it had freezed because it stood still at 'formating system' but later continued.
The bootloop occurred when I tried rooting the ROM so don't root it yet after installation.
-Please how do we fix the led notification bug?
Click to expand...
Click to collapse
I wrote clearly in the thread that flashing take time, I told you to be patient, but people do not read
No fix for notification LED bug at the moment, I'll try to fix it...
Finally, this is great guys.[emoji106] thanks @Nonta72 and all.
Sent from my D5110-X510 using Tapatalk
Smooth ROM
This ROM is by far one of the best for Hot 2, well done.
As with most of the ROM you ported, rooting is unavailable , so might be difficult to fix led bug on our own.
SD card works.
USB mode works...every other thing except LED.
Rocking this at the moment.
negga4al said:
This ROM is by far one of the best for Hot 2, well done.
As with most of the ROM you ported, rooting is unavailable , so might be difficult to fix led bug on our own.
SD card works.
USB mode works...every other thing except LED.
Rocking this at the moment.
Click to expand...
Click to collapse
Flash marshmallow compatible supersu in recovery!
Root is an easy job
Nonta72 said:
Flash marshmallow compatible supersu in recovery!
Root is an easy job
Click to expand...
Click to collapse
Unfortunately, people on facebook reported that it bootloops after flashing systemless root, and normal root is not working; it doesn't grant permissions
I'm looking into it, but not sure if there is something I can do.
The ROM is good with a but, could it be possible toake it easy for everyone to use cos most ROMs work well on android one so flashing is nothing.
But when one had to revert first to infinix ROM meh its not very encouraging knowing d data lose involved.
So if its possible to bring it down pls try.
Or make d infinix ROM flash able on android one...