Ubuntu touch for the galaxy tab a 2016 wifi and galaxy tab a 2016 lte (untested)
Code:
/*
* 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.
*/
What is it?
As the title said, this is Ubuntu touch for the galaxy tab a 2016, a GNU/Linux os.
What is Ubuntu Touch?
Ubuntu Touch is the touch-friendly mobile version of Ubuntu.
This operating system is developed and maintained by UBports: An international community of passionate volunteers.
This means Ubuntu Touch is 100% community driven and independent.
What is Halium?
Halium is the collaborative project to unify the Hardware Abstraction Layer for projects which run GNU/Linux on mobile devices with pre-installed Android.
/!\ This is NOT an android based OS, android apps wont run without anbox (currently unavaible). Do NOT flash magisk, gapps or any android related zip on top of it.
What's working:
Actors: Manual brightness
Sensors: Touchscreen
Sensors: Rotation
Network: WiFi
Misc: Battery percentage
Misc: AppArmor patches applied to kernel (Kernel 3.4, 3.10, 3.18)
Misc: Shutdown / Reboot
Misc: RTC time is used after reboot
Working with additional steps:
GPU: Boot into UI
What's not working:
Only 5 apps works, will try to fix it
Problems with waking from sleep.
Misc: Anbox patches applied to kernel
Misc: Offline charging
Sound: Earphones
Sound: Loudspeaker
Sound: Microphone
USB: MTP access
-- Will not work due to the treble port breaking them --
Sensors: GPS - SM-T580 only
Sound: Volume control
Untested:
Actors: Torchlight
Camera: Flashlight
Camera: Photo
Camera: Video
Camera: Switch between back and front camera
Cellular: Carrier info, signal strength - SM-T585 only
Cellular: Data connection - SM-T585 only
Cellular: Incoming, outgoing calls - SM-T585 only
Cellular: MMS in, out - SM-T585 only
Cellular: PIN unlock - SM-T585 only
Cellular: SMS in, out - SM-T585 only
Cellular: Change audio routings - SM-T585 only
Cellular: Voice in calls - SM-T585 only
Endurance: Battery lifetime > 24h from 100%
Endurance: No reboot needed for 1 week
GPU: Hardware video decoding
Misc: Online charging
Misc: Recovery image
Misc: Reset to factory defaults
Misc: SD card detection and access - only for devices that support it
Network: Flight mode
Network: Hotspot
Sensors: Automatic brightness
Sensors: GPS - SM-T585 only
Sensors: Proximity
(USB: ADB access - disabled atm due to no middleware)
How to install:
https://github.com/antoine62/android_kernel_samsung_exynos7870/wiki/How-to-install
How to update:
TODO
Tanks to:
@Valera1978 for the treble port & everybody who contribued to it
@CactiChameleon9 for helping me
The ubports team
Status:UNSTABLE
Kernel sources: https://github.com/antoine62/android_kernel_samsung_exynos7870/
Reserved
Reserved2
Holy cow been waiting for this can't wait to flash!! Thank you
twfs said:
Holy cow been waiting for this can't wait to flash!! Thank you
Click to expand...
Click to collapse
Its unstable currently, but i will fix the bugs! And i may have found why audio doesnt work on treble, so audio will be working one day, like everything else
Thanks for all this work, I hope you can fix the mistakes
I somehow fixed touch not working after waking up by building it using the full halium sources, i will soon make a new release, and im still searching why apps doesnt work.
Offline charging and bluetooth may be easy to fix too.
EDIT: Nvm its still broken
I think that i will retry to build halium using the lineage-16.0 branch, using the outdated treble port will just bring issues, and i may have know why the system image didnt worked: i used the wrong rootfs & i didnt apply patches...
antoine62 said:
I think that i will retry to build halium using the lineage-16.0 branch, using the outdated treble port will just bring issues, and i may have know why the system image didnt worked: i used the wrong rootfs & i didnt apply patches...
Click to expand...
Click to collapse
Wait for these fixes and thank you for all the work and I hope it's a good ROM
I got the system image to build without errors, so this mean that we will not need the treble port anymore, but apparently the halium7 rootfs installation is different from the halium9 version.
antoine62 said:
I got the system image to build without errors, so this mean that we will not need the treble port anymore, but apparently the halium7 rootfs installation is different from the halium9 version.
Click to expand...
Click to collapse
Very excited to try it
I installed the rom by following all the exact same steps but apparently when I try to start some apps such as file manager, openstore, terminal etc. they immediately crash.
I don't really know how could I solve the problem.
Any help?
Chuppah_ST said:
I installed the rom by following all the axact same steps but apparently when I try to start some apps such as file manager, openstore, terminal etc. the immediately crash.
I don't really now how could I solve the problem.
Any help?
Click to expand...
Click to collapse
Wait for a fix, its "normal". That's why the rom is unstable. I'm working on fixing this when i have some free time, and i dont have a lot of free time currently.
It may also be fixed on the non-gsi build that i cant install curently
antoine62 said:
Wait for a fix, its "normal". That's why the rom is unstable. I'm working on fixing this when i have some free time, and i dont have a lot of free time currently.
It may also be fixed on the non-gsi build that i cant install curently
Click to expand...
Click to collapse
there is a non-gsi build?
Chuppah_ST said:
there is a non-gsi build?
Click to expand...
Click to collapse
Yes, not released currently.
That's what i was doing during the last 2 weeks.
It will be easier to debug this one because i have more control over the vendor and there's no problem with sound and gps.
I may stop building for smt-585, because modem will never work if i cant debug it, and maybe the same thing for gps, and the sm-t580 versikn should work on the sm-t585.
antoine62 said:
Yes, not released currently.
That's what i was doing during the last 2 weeks.
It will be easier to debug this one because i have more control over the vendor and there's no problem with sound and gps.
I may stop building for smt-585, because modem will never work if i cant debug it, and maybe the same thing for gps, and the sm-t580 versikn should work on the sm-t585.
Click to expand...
Click to collapse
sad cuz I have sm-t585
Chuppah_ST said:
sad cuz I have sm-t585
Click to expand...
Click to collapse
+1 i have sm-t585
I may build for the sm-t585 then, but you will need to help me to debug ril if you want it. Anyway, before doing this, i need to debug halium9 because the non-gsi build doesnt boot to ui (black screen, no spinner), but it boots to ubuntu touch and usb work
antoine62 said:
I may build for the sm-t585 then, but you will need to help me to debug ril if you want it. Anyway, before doing this, i need to debug halium9 because the non-gsi build doesnt boot to ui (black screen, no spinner), but it boots to ubuntu touch and usb work
Click to expand...
Click to collapse
For sure i'll help you, maybe we could chat on telegram to make things easier, don't knoe.
antoine62 said:
I may build for the sm-t585 then, but you will need to help me to debug ril if you want it. Anyway, before doing this, i need to debug halium9 because the non-gsi build doesnt boot to ui (black screen, no spinner), but it boots to ubuntu touch and usb work
Click to expand...
Click to collapse
i'll help you
Chuppah_ST said:
For sure i'll help you, maybe we could chat on telegram to make things easier, don't knoe.
Click to expand...
Click to collapse
Sure, i may do a bridged discord channel/matrix room/telegram group soon, but first i need to gt the non-gsi version to boot to gui.
Related
This ROM is heavily updated and still being developed at a fairly rapid pace.
The update process is now very simple to do
PLEASE NOTE: THEIR ARE NOW 2 BUILDS BEING RELEASED FOR EACH UPDATE, ONE IS A NEWBASEBAND VERSION WHICH WILL WORK WITH ANY BASEBAND AFTER 1.2 OR ANY OFFICIAL DELL FROYO BASEBAND, THE OTHER IS A NO-BASEBAND UPDATE DESIGNED FOR REBELSIM USERS AND REQUIRES THE 2.1 8105 BASEBAND
The recommended Update requires you to upgrade your device baseband, this is a simple procedure via fastboot.
rebelsim users should use only the nobaseband update file and use the 2.1 baseband or they will encounter problems
We now have a nice new website blog for streakdroid - check it out and help me populate the wiki with faqs and get in the forums sites @ http://www.streakdroid.com
Most Recent Version: v1.5.3
Known Issues:
Accelerometer is dodgy at times but i cant pin down the issue - usually going into settings > display and toggling auto rotate on and off fixes
-----------------
Changelogs
-----------------
UPDATE 6/1/2011
Version 1.5.3 AKA Biscuit Madness
Added new Transparent statusbar and gingerbread style theme (based off quikt's transparent theme on xda)
Removed setcpu due to issues with it being preinstalled
Updated streakradio
Readded front camera support to cam app - fring support removed
Played with audio libs a little. probably wont fix anything
Added new bootanimation courtesy of darksmurf
Added BatteryWidget app to allow seeing battery percentage as its not easily possible on the gingerbread battery icon (add The widget to a desktop somewhere) - also allows quick access to some settings
UPDATE 2/1/2011
Version 1.5.2 AKA Insect Roadkill
Added Gingerbread Style battery Icon with Percentage(looks SOO much nicer than the stupid looking circle icon)
Changed some Colors in status bar
Updated Google Maps, Twitter, G-Mail, Launcher Pro, Miren Browser And Market to Latest versions according to my device.
Added Some more TCP/networking tweaks
Reduced the level of audio boost set in kernel, may help the volume issues.
Added Fixed Email.apk for exchange 2010 sp1 support
Fixed Twist Rotate & Two Finger altitude adjust in Google maps
Streak Light Pre-installed (untested)
SetCPU Preinstalled
Music App Replaced With version Suggested in this topic to fix the pause error.
MIUI Music app Added
Universal Androot removed, Rom is PRE-ROOTED
UPDATE 15/12/2010
Version 1.5.1 AKA Animadness
Fixed Wifi Tethering
Fixed Settings Force Closes
Reverted market as official update will be pushed to device soon
Kernel From perfmod added, (1.267ghz max oc)
New Fonts Courtesy Of Kang-O-Rama rom for nexus one
New Window Animations
GPS SHOULD be sorted - remember to update baseband
UPDATE 11/12/2010
Version 1.5.0 AKA FaceTime Edition
Fixed USB Tethering - works properly now
Fixed Notifications Settings
Reverted Camera Frameworks and app to 1.1.1 version to allow front cam in fring etc (works and tested in fring)
Added GingerBread Market
Added GingerBread KB
Added Miren Browser
Probably Loads Of Other Things I Have Forgotton
Reckon this is pretty much 100% stable now
UPDATE 25/11/2010
Version 1.4.6 AKA Swappable Goodness
Fixed USB Tethering
Reverted Market App due to force Closes
Removed Check for Rear Panel Placement(Device WILL run with no panel in place - also see Note 2)
Added Fards Data Tweaks(see Note 1 below)
Removed 128Mhz Clock speed due to reports of crashes
Reenabled 1.19 ghz clock
---------------------
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.
*/
Please feel free to donate to my work if you find it useful - any amount is appreciated
GBP Donate | USD Donate
-------------------
Required Files
-------------------
Rom Download Links:
New BaseBand Version
Primary Download Site: http://downloads.streakdroid.com/djsteve/update-1.5.3.zip
Mirror 1: http://www.android-roms.com/downloads/upda...pdate-1.5.3.zip
Mirror 2: http://mirror2.streakdroid.com/update-1.5.3.zip
IT IS HIGHLY RECOMMENDED TO UPDATE TO THE BELOW BASEBAND FOR 1.5.1+
Baseband File Download:
Primary Download Site: http://downloads.streakdroid.com/djsteve/amss.mbn
Mirror 1: http://www.android-roms.com/downloads/updates/amss.mbn
Mirror 2: http://mirror2.streakdroid.com/amss.mbn
NOBASEBAND Version
Primary Download Site: http://downloads.streakdroid.com/djsteve/u...-1.5.3-nobb.zip
Mirror 1: http://www.android-roms.com/downloads/upda...-1.5.3-nobb.zip
Mirror 2: http://mirror2.streakdroid.com/update-1.5.3-nobb.zip
VPN USERS: TUN.KO for you is below.
http://build.streakdroid.com/tun.ko
if you have NOT already flashed the dell 2.2 pkg or my 720p fix you need this to fix 720p video - otherwise ignore
http://downloads.streakdroid.com/testing/dsp1.mbn
flash this using the fastboot command fastboot -i 0x413c flash dsp1 dsp1.mbn
-------------------
Other Requirements
-------------------
Some Common Sense
Pinch of Good Luck
Patience
Ability to read and follow instructions
Fastboot Setup and Working
ClockworkMod Recovery Flashed and working
-------------------
Level Of Difficulty
-------------------
8/10 - Easy level, should be simple enough for 99% of users to complete
-------------------
How-To
-------------
1. Copy the update zip to your memory card first
Steps 2-4 are only needed if you are coming from a build OLDER than 1.2
2. Power down your streak and boot into fastboot
do this by pressing power until the keypad lights come on then HOLD camera until you get to a white screen, then tap on the fastboot text in top right corner,
3. Connect your streak to pc - the text on streak should change to FASTBOOT_MODE.
you should place the amss.mbn file into the same folder as fastboot on your pc
run the following commands from command prompt on your pc
Windows:
Code:
fastboot -i 0x413c flash amss amss.mbn
Linux
Code:
fastboot flash amss amss.mbn
4. Type the following commands to reboot your streak - again alow it to boot into the main ui - you will lose network connection for the moment, this is fine, also streak WILL reboot twice before booting, again this is normal
Windows:
Code:
fastboot -i 0x413c reboot
Linux
Code:
fastboot reboot
5. Once your device has booted shut down again and boot into clockwork recovery by doing the following
boot to recovery as per step 1 then choose option 2.
6. Flash the 1.5 update zip
7. reboot
Thanks to:
Everyone for suggesting things they want adding
android-roms for the mirror
Vinokirk for helping diagnose and sort out 2.1 baseband ril support and gps
Andycap & fards for providing modified Gps.conf
homeiss forthe excellent upgrade/downgrade guide
everyone else for just jumping in and helping each other, thats the true community sprit that makes me do this sort of dev for android and not some other mobile os.
everyone else who helped/is helping
hopefully thats everything
any issues theirs me and a few of my tech head irc helpers keeping an eye on the posts. or just jump in the irc channel #dellstreak on freenode for help.
also please feel free to donate to my work if you find it useful - any amount is appreciated
GBP Donate | USD Donate
Congrats Steve! This guy has put a *lot* of hours into getting this working for us. Give a small gift or donation if you like the ROM.
Im on Uk bought Dell unlocked currently with 6941 2.1 rom
will this work on my streak?
thanks
well im on a uk o2 streak and it works fine here
so it should work on any streak?
well we have tested it on a few streaks now and its worked fine,
ok cheers will give it a bash......................ps where do u live if it fubars and i need a refund on my fone?
Nice work Steve much appreciated you have worked hard on this project i will give it a sticky
lufc said:
Nice work Steve much appreciated you have worked hard on this project i will give it a sticky
Click to expand...
Click to collapse
cheers buddy
how do you install the driver on windows 7 x64? i tried going into the devices panel and updating the driver to the stuff in the folder, but none of them would work. any suggestions?
sorry, i think i need to be a little more clear. i read through the pdf, but the info is mostly for xp and doesn't apply to 7 at all. when i'm done adding the unknown device to device manager as android composite device, i don't get com ports like they do, so i cant flash it at all. any thoughts?
i would highly suggest people use windows xp or 7 32bit for flash as 64bit is a pain, win xp mode is avail for 7
Worked great on my US streak with 8105 rom.
For people having problems with Win 7, try running QDLtool.exe as administrator and also try different USB port.
I assume that flashing back the baseband to the stock version is not possible, right? If so, will the Android 1.6 stock FW work with that new baseband? In other words: Is it or is it not possible to go back to the stock FW (just in case) after performing this 2.2 update?
does tha front facing camera working in this build?
how would I do this using Ubuntu 10.4
how would I do this using Ubuntu 10.4, dell streak I also have already "bricked" 1 streak. well kinda, it won't go pass the dell logo, but I can get to fastboot. Really feel like I own a Lamborghini but can only drive it 15mph.
lrevell8 said:
how would I do this using Ubuntu 10.4, dell streak I also have already "bricked" 1 streak. well kinda, it won't go pass the dell logo, but I can get to fastboot. Really feel like I own a Lamborghini but can only drive it 15mph.
Click to expand...
Click to collapse
that streakflash only works in windows. so you will need to get a machine with xp or run a live distro. the rest of the rom is flashed through fastboot so you can recover it.
hey steve glad to see you managed to get froyo on it, iv donated a small amount but hey every little goes a long way huh? just wanted to ask, now that you have succeeded with this, does it open the doors for more custom froyo roms? like i would really like to see a htc skinned froyo with the 30fps cap removed, im not asking you to do it (before i get flamed), m just asking is it now possible?
lol im working on cyanogenmod
oh i forgot to mention folks THIS BUILD IS FPS UNLOCKED !!!!!!!!
DJ_Steve said:
lol im working on cyanogenmod
oh i forgot to mention folks THIS BUILD IS FPS UNLOCKED !!!!!!!!
Click to expand...
Click to collapse
God bless you stevy
I shall wait for once its done but fantastic work.
/manlove
Wow great work!!!
Sorry about this question but what do I have to do with the boot system and userdata images to flash it with fastboot?
Sorry had only wm devices before
Team Win Recovery Project
for Huawei Mediapad s7-301u
What's new in 2.8.4.0:
- Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
- Fix some MTP related crashes and bugs
- Eliminate TWRP toggling USB IDs during boot if MTP is enabled
- Fix various adb sideload issues
- Improve threading of actions
- Eliminate separate thread for screen timeout
- Update libblkid to 2.25.0
- Use power button as back button on watch themes for easier navigation
- Add mutex locking to data manager
- Improve custom theme handling on encrypted devices
- Allow the stock theme to be offset by build flags so we can center a lower res theme on a higher res screen especially for watches with round screens
SS:
Download
https://drive.google.com/file/d/0B-JwjbrlsO9CbUpyOHQtSGs4ak0/view?usp=sharing
Installation :
It's automatic
- Be sure that you have checked this points :
- on you computer : install huawei usb driver
- on your phone : enabled USB Debuging in
- Settings-Developer options-USB debugging on your tablet
credit : Dees_Troy, TheMasterMindGT
Hello,
Unfortunatelly the google drive link in the OP does not appear to work for me. It reports 404 error to me.
pvdeejay said:
Hello,
Unfortunatelly the google drive link in the OP does not appear to work for me. It reports 404 error to me.
Click to expand...
Click to collapse
Done, Link Update
ary12282 said:
Done, Link Update
Click to expand...
Click to collapse
Someone has tested the Huawei Mediapad S7-302u
TheMasterMindGT said:
Someone has tested the Huawei Mediapad S7-302u
Click to expand...
Click to collapse
according to this http://forum.xda-developers.com/showthread.php?t=1743025, there is no difference between those two versions, except the radio freq, so i think you can safely flash the recovery
Hello,
I have flashed this hoping I will be finally able to control TWRP using commandline. That's a new feature added in TWRP 2.8. However most likelly because of the core MTP support ADB is not turned on as this version of TWRP boots up.
I am unable to use TWRP GUI because I'm blind, so I had to revert back to TWRP 2.7.1 in order to get ADB functional in the recovery by default.
This is my strange use case only I think you will have no issues with this. You should safelly flash this using fastboot or flashify if you have got rooted your tablet.
install this recovery to Huawei MediaPad 7 S7-302u but shows no navigation buttons, so it does not work for the model Huawei MediaPad 7 S7-302u.
ary12282 said:
Done, Link Update
Click to expand...
Click to collapse
Hi @ary12282,
I this TWRP still available? Seems the link to google drive requires permission?
Thank you!
Edit:
Hi @pvdeejay and @TheMasterMindGT,
any chance one of you still have a copy of the TWRP 2.8.4.0 for the S7-301u on hand, which you can share?
Thank you!
TOTALLY EXPERIMENTAL ONLY FOR TEST
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.
Click to expand...
Click to collapse
Working :
- graphics, sound, touch screen
- sim card, mobile data, voice calls
- internal memory, sdcard
- wifi, bluetooth
- flashlight/torch
- camera
- fingerprint
- nfc
- battery percentage (fast charging, confirmed)
Not working :
- notification leds
- wrong battery percentage
- auto brightness
- tethering
- earphone not detected
- other not tested functionalities
How to install :
- Unlock your phone
- Download the CyanogenMod zip(s). (cm-13.0-20160916-UNOFFICIAL-passion_row.zip) Updated link
- Copy the CyanogenMod zip to internal or external sdcard.
- Install a compatible Recovery. (TWRP 3.0.2.0, CM) MUST INSTALL!!
- Boot into Recovery.
- Do a Factory Reset. (Wipe data & cache), SAVE YOUR DATA
- Flash CyanogenMod.
Optional:
- Install the Google Apps addon package (chose ARM64).
Device : https://github.com/kyotr/android_device_lenovo_passion_row
Kernel : https://github.com/kyotr/android_kernel_lenovo_passion_row
Vendor :https://github.com/kyotr/android_vendor_lenovo_passion_row
Hey anyone tried this rom?
While installing I am getting error like "This rom is for passion_row. Your device name is idol347." Can anyone tell me what is wrong?
daniyalhasan said:
Hey anyone tried this rom?
While installing I am getting error like "This rom is for passion_row. Your device name is idol347." Can anyone tell me what is wrong?
Click to expand...
Click to collapse
first you need to install new a recovery file, use fastboot to install one of these recoveries (TWRP, CM)
Command: fastboot flash recovery filename
Click to expand...
Click to collapse
Can you confirm whether this ROM contains VOLTE feature or not? Is there anything else you got not working? Share your experience please.
I also got the same error. Used twrp. Do I have to use yet another recovery?
mifiik said:
I also got the same error. Used twrp. Do I have to use yet another recovery?
Click to expand...
Click to collapse
Will only work with recoveries provided here . other recoveries ARE NOT COMPATIBLE
Ok, I'm going to try. I'll report. Thanks
After using suggested recovery I'm up and running. Besides bugs from the first post I found brightness not working (neither automatic nor manual) and some apps from the Play Store not able to install due incompatible.. (Chrome and some others). Wifi hotspot also not working. Everything else seems to be OK. Good job done!
Thanks for starting your work on this. Keep up the good work
Sent from my Lenovo P1a42 using XDA-Developers mobile app
My observations:
Wifi tethering and usb tethering not working.
Built in root not working(though triggered under developer options)
Automatic brightness not working(though brightness slider working flawlessly)
Notification LED not working
Great work @_kyo_ ....... kudos[emoji106] [emoji106]
Super su works.
Battery charging is slow . It would be nice if this issue is resolved . Thank you.
awesome work,
glad to see developments, 1st custom rom fr vibe p1
though few bugs i observed over previously notified by others,
-Coudn't unlock using fingerprint
i could register my my FP but when i try to unloack, it vibrate fr one time with error following no responce
-call volume cannot be adujusted
both in normal speaker n loud speaker mode
-headphone or earphones r not detected
Fingerprint unlock forks for me. I noticed volume adjustment problem too.
all bugs list till now
1-notification leds
2-wrong battery percentage
3-brightness not working >>>> automatic only
4-some apps from the Play Store not able to install due incompatible
5-Wifi hotspot also not working
6-Wifi tethering and usb tethering not working
7-Built in root not working >>>>> fixed by super su
8-Battery charging is slow
9-Coudn't unlock using fingerprint worked well
10-call volume cannot be adujusted
11-headphone or earphones are not detected
Click to expand...
Click to collapse
mohamed abd elmoaety said:
all bugs list till now
1-notification leds
2-wrong battery percentage fixed using gravity box
3-brightness not working >>>> automatic only
4-some apps from the Play Store not able to install due incompatible
5-Wifi hotspot also not working
6-Wifi tethering and usb tethering not working
7-Built in root not working >>>>> fixed by super su
8-Battery charging is slow
9-Coudn't unlock using fingerprint worked well
10-call volume cannot be adujusted
11-headphone or earphones are not detected
Click to expand...
Click to collapse
Please how did you fix the battery percentage bug with gravitybox? Thanks
Hello, this ROM is compatibile which version of Lenovo P1?
Vibe P1 P1a42
Vibe P1 P1c58
Vibe P1 Pro P1c72
or... Vibe P1 Turbo ?!? Thank you very much for the support
pickmod said:
Hello, this ROM is compatibile which version of Lenovo P1?
Vibe P1 P1a42
Vibe P1 P1c58
Vibe P1 Pro P1c72
or... Vibe P1 Turbo ?!? Thank you very much for the support
Click to expand...
Click to collapse
Vibe P1 P1a42
@_kyo_ is this ROM built from source or ported using copy paste methods? And was it really necessary to force a random name as the device name to make people use your custom recoveries? If you have source built any of the recovery or ROM can you please release your sources?
Ambient display also not working.
The Developer Preview has ended. The official release has been released and can be found here https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265
The current (unofficial) Developer Preview is developed by @erfanoabdi This thread serves as a means to help folks from further discussing LOS16 within the Official Lineage 15.1 thread (to help prevent that thread from being both further hijacked and to prevent confusion from the two in conversation).
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Code:
/*
* 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.
*/
Please remember this is NOT a final release. There WILL be bugs. It is also very possible that you could end up bricking your phone by attempting to install, use, or upgrade LOS16 and you do so at your own risk.
How to install Lineage 16.0 Developer Preview
!! Please read in full before proceeding !!
Remember to submit logs when reporting any errors.
Remember to be as detailed and as clear as possible on what actions you took which resulted in any errors.
Download the latest Official TWRP https://dl.twrp.me/payton/. - You want the .img file.
Restart your phone to your bootloader. - You do this by pressing and holding both your phone's power button and the lower volume key at the same time.
Once at your phone's bootloader, from your Windows Command Prompt (as administrator) or from your Linux Terminal (as root) run the following command to load TWRP:
Code:
fastboot boot '/your_path_here/twrp-X.X.X-X-payton.img'
Note: Be sure to use your path on where you have the file on your computer. Be sure to replace and use the correct file name for your file (Do not just copy and paste example posted here).
!! You will be wiping everything because this is a developer preview and bug reports are most helpful on a clean, fresh install !!
Regardless of what ROM you are coming from (stock or not), format your DATA.
Reboot your device to bootloader and reuse the previous fastboot command to load TWRP listed above.
Regardless of what ROM you are coming from (stock or not), wipe your device (all partitions).
Reboot your device to bootloader and reuse the previous fastboot command to load TWRP listed above.
Download "Copy Partitions Zip" - courtesy of @filipepferraz https://drive.google.com/file/d/1oiry9UfP2tf-5A6nQBF7pn2t2eSGKt0F/view
Upload "Copy Partitions Zip" to your phone using the "ADB Push" command to /sdcard/ (run as admin if on windows or as root if on Linux).
Code:
adb push copy-partitions-payton.zip /sdcard/
Now INSTALL "Copy Partitions Zip"
Reboot to your bootloader. - Stay at the bootloader screen (do not load TWRP)
Download the firmware for your phone
XT1900-1 Android 8.0
firmware_27.251.12_payton_retail_xt1900-1.zip
Only tested on
XT1900-1
XT1900-2
XT1900-5 (https://forum.xda-developers.com/showpost.php?p=76934354&postcount=173)
XT1900-7 (https://forum.xda-developers.com/showpost.php?p=76779696&postcount=14)
feel free to test on other Moto X4 models running 8.0.
XT1900-6 Android 8.0 - courtesy @filipepferraz
https://www.androidfilehost.com/?fid=674106145207492371
XT1900-1 Android 8.1 - courtesy @ptn107
https://www.androidfilehost.com/?fid=890278863836292604
tested on XT1900-7 as well (https://forum.xda-developers.com/showpost.php?p=76816113&postcount=92)
Latest firmware for payton_fi android 9 from PPW29.69-26 - courtesy @ptn107
firmware-29.69-26_payton-fi_xt1900-1.zip
Unzip on your computer.
User flash_all.bat if on windows as administrator OR ./flash_all.sh if on Linux as root.
Reboot your phone to bootloader
Reboot your device to bootloader and reuse the previous fastboot command to load TWRP listed above.
Download and locate the latest developer preview: https://androidfilehost.com/?w=files&flid=281597
You will upload these files to your phone using the "ADB PUSH" command to your /sdcard/ directory (as admin in windows or root in Linux). For example:
Code:
adb push lineage-16.0-20180921-UNOFFICIAL-payton.zip /sdcard/
Install your ROM.
Congratulations! You're done!
NOTE: The point of using a developer preview is to test the ROM itself. You can attempt to install TWRP after installing your ROM, just as you can reboot back to recovery after, and install OpenGapps, followed by Magisk, but that is NOT the true point of testing this ROM. While it may be useful to know of issues with those commonly used tools, the primary concern is the ROM itself at this time.
Remember to submit logs when reporting any errors.
Remember to be as detailed and as clear as possible on what actions you took which resulted in any errors.
MotoX4 said:
Remember to submit logs when reporting any errors.
Remember to be as detailed and as clear as possible on what actions you took which resulted in any errors.
Click to expand...
Click to collapse
Excelent Rom very good accuracy of battery, but usb adb is not working
Hi @erfanoabdi, I am really enjoying this ROM.
Question: Is there any way to replicate the Retail X4's One Button Nav? It seems to have implemented a press/long-press/longer-press for the fingerprint scanner. Not sure if something like this is in the AOSP code or not. It is really awesome for locking screen AND keeping Google Assistant.
---------- Post added at 08:05 PM ---------- Previous post was at 07:18 PM ----------
I have played around a it with flashing Generic System Images (GSI) over this ROM, and it seems to be quit compatible most of the Android 9 ones that I have tried.
It is awesome that this phone suddenly has many options to toy with (yes, I said it, it is a toy) due to the hard work of the devs Trebelizing (or is it Treble-izing?) our Moto X4!
---------- Post added at 08:09 PM ---------- Previous post was at 08:05 PM ----------
vmmiguel said:
Excelent Rom very good accuracy of battery, but usb adb is not working
Click to expand...
Click to collapse
USB ADB seems to be working fine for me. I am on the 9/29 version.
jhedfors said:
Hi @erfanoabdi, I am really enjoying this ROM.
Question: Is there any way to replicate the Retail X4's One Button Nav? It seems to have implemented a press/long-press/longer-press for the fingerprint scanner. Not sure if something like this is in the AOSP code or not. It is really awesome for locking screen AND keeping Google Assistant.
---------- Post added at 08:05 PM ---------- Previous post was at 07:18 PM ----------
I have played around a it with flashing Generic System Images (GSI) over this ROM, and it seems to be quit compatible most of the Android 9 ones that I have tried.
It is awesome that this phone suddenly has many options to toy with (yes, I said it, it is a toy) due to the hard work of the devs Trebelizing (or is it Treble-izing?) our Moto X4!
---------- Post added at 08:09 PM ---------- Previous post was at 08:05 PM ----------
USB ADB seems to be working fine for me. I am on the 9/29 version.
Click to expand...
Click to collapse
For me doesn't work, nothing appears in notificacions bars or even in fastboot can´t recognize my device...
Actually i have running this rom, but i don´t have GAPPS installed, and the adb is not working so i cant flash via fastboot the twrp for install my gapps, any suggerency to do?:good::crying:
jhedfors said:
Hi @erfanoabdi, I am really enjoying this ROM.
Question: Is there any way to replicate the Retail X4's One Button Nav? It seems to have implemented a press/long-press/longer-press for the fingerprint scanner. Not sure if something like this is in the AOSP code or not. It is really awesome for locking screen AND keeping Google Assistant.
Click to expand...
Click to collapse
Thanks for using this rom but you can enable it from
Setting system buttons and disable on screen nav bar
I couldn't get long hold and longer hold to detect in custom roms but still it's usable for home recent and back buttons
You can set hold home button to action something else then assist (lockscreen)
erfanoabdi said:
Thanks for using this rom but you can enable it from
Setting system buttons and disable on screen nav bar
I couldn't get long hold and longer hold to detect in custom roms but still it's usable for home recent and back buttons
You can set hold home button to action something else then assist (lockscreen)
Click to expand...
Click to collapse
Thanks. I am using the fingerprint navigation as you describe. I am using an app that detects a double-tap, which I am using to lock the screen.
Sorry for OT:
Is there any way to take the long-press away from Google Assist (and be able to re-assign it) short of UN-installng Google? When I "disable" it in the Google App, or even change the default assist app, long press fingerprint only prompts to re-enable Google Assist. It seems those settings only apply to long-press Home, but not long-press fingerprint. Google Assist has hijacked my fingerprint button!
Thanks again.
jhedfors said:
Thanks. I am using the fingerprint navigation as you describe. I am using an app that detects a double-tap, which I am using to lock the screen.
Sorry for OT:
Is there any way to take the long-press away from Google Assist (and be able to re-assign it) short of UN-installng Google? When I "disable" it in the Google App, or even change the default assist app, long press fingerprint only prompts to re-enable Google Assist. It seems those settings only apply to long-press Home, but not long-press fingerprint. Google Assist has hijacked my fingerprint button!
Thanks again.
Click to expand...
Click to collapse
I disabled the "google" application and stopped bothering with activating it again, it was the only way I found, because if you deactivate the assistant only when you keep it pressed the sensor sends the message to activate it xD
vmmiguel said:
Excelent Rom very good accuracy of battery, but usb adb is not working
Click to expand...
Click to collapse
I hope somebody to help me, last night i tried to update mi Lineage OS 16 (from erfanoabdi).
My device is unlocked bootloader, and i used the rom from nightly build (2018-21-09), it works fine and everything, the issue becomes when i look what was avaible a new update, so downloaded and install the new rom.
I do full wipe, after that i install the new rom, at this point everything its working fine, but after that when i changed the partition slot from A to B.
When i started to install the gapps they closed because it says what i am running Android 8.0, but its a mistake so i think that reboot the phone without install the gapps. So the phone starts well, so i decide again to boot into recovery (TWRP) to install the missing gapps.
When the device reboot in fastboot and i chosee the recovery option, the surprise was that TWRP was reemplaced by the stock recovery, and when i tried to flash the TWRP.img my device wont appear in fastboot mode, stays finding device and Windows wont recognized my phone.
I think the rom still no have usb adb support, so i cant flash TWRP
My device its unlocked and i was running the rom (but another nightly) .. without issues for a week ago... until i flashed this one
Now i have Lineage OS without GAPPS, without USB mode... Like the update from OPW 27 or 28 idk remember.
Thanks for read this i hope somebody can help me.
My device its a XT1900-4 in Android 9.0 without google apps, only have the essencial apps like phone dialer , sms, the very very essencials app. Like an phone from 2008 jhaha
I attach some information photos from the Rom that im running:
(System Running) fine thanks
https://ibb.co/bXC7ye
(ADB is switched on, but no appears nothing)
https://ibb.co/exGpBz
(I tried with everyone of the opcions
https://ibb.co/ekv5jK
and this is my currently fastboot:
AP Fastboot Flash Mode (Secure)
BL: MBM-3.0-uefi-641a15b-180224
Baseband: M660_7042.27.01.74R PAYTON_LATAM_CUST
Product/Variant: payton xt1900-4 32GB P4
CPU: SDM630 1.0 (6)
Console [NULL]: null
Tools Mode Config: DISABLED
POWER OK
flashing_unlocked
Software status: Official
Transfer Mode: USB Connected
At this point my windows so says to my device is Error in a request for the USB device descriptor.
i tried last_usb_google driver.
Motorola Device manager 2.5.4
Minimal adb fastboot 1.4.2
and nothing works fine.
In my recovery appears this:
Android Recovery
motorola/payton/payton
8.0.0/OPW27.57.25-6-10/12
user/release-keys
Use volume to...etc and then i used the (Apply update from adb)
says:
Supported API: 3
Stopping adbd. . .
Now send the package you want to apply to the device with "adb sideload <filename>"
I tried to navigate in the device with the terminal app, so i put this command in terminal to make ADB run
command adbd, and this appears on terminal:
adbd E 10-04 23:01:31 3819 3819 adbd_auth.cpp183] Failed to get adbd socket: success
adbd E 10-04 23:01:31 3819 3819 adbd_auth.cpp183] Failed to get adbd socket: success
i try to run command logcat.txt, but terminal cant move to sdcard.
i try to adb over network and that connect but can´t do anything because stuck on <waiting device>, i look the blankflash but
didn´t works to me, and in the configurations usb settings looks greyed so cant switch between then.
when i run the command ls i saw this files:
init.usb.configfs.rc
init.usb.rc
init.recovery.qcom.usb.rc
maybe there is my problem? Thanks for read, thanks to @erfanoabdi he works very hard to make this possible, i hope somebody can
help me.
vmmiguel said:
I hope somebody to help me, last night i tried to update mi Lineage OS 16 (from erfanoabdi).
...
When the device reboot in fastboot and i chosee the recovery option, the surprise was that TWRP was reemplaced by the stock recovery, and when i tried to flash the TWRP.img my device wont appear in fastboot mode, stays finding device and Windows wont recognized my phone.
...
Click to expand...
Click to collapse
Not sure if I understood all of your post.
On the MotoX4 there is no separate partition for the recovery, it is build into the system boot image / ramdisk. If you flash a new LineageOS or a new kernel youre TWRP is gone. So before you boot, you have to reflash TWRP. If you forgot to do this, you have to bring your device to fastboot mode (Volume down + Power 'till it boots to fastboot mode). Then boot it by "fastboot boot twrp-3.2.3-1-payton.img" to TWRP. If it has booted to TWRP recovery only then you can "adb push twrp-install-xxxx-payton.zip /sdcard" and install it from recovery. After that you should be able to directly reboot to recovery and flash what you need.
I always have all required "xxx.zip" on my microSDcard, so that I can flash them from TWRP without sideload or adb push. Remember to reboot to recovery after every "xxx.zip" flashed because of the A/B design of the MotoX4.
---------- Post added at 09:46 PM ---------- Previous post was at 09:41 PM ----------
Anybody else?
WLAN for me does not connect on lineage-16.0-20180929-UNOFFICIAL-payton.zip, if you have a hidden network (SSID). It will be shown as "saved" but does not try to connect.
Worked on lineage-16.0-20180921-UNOFFICIAL-payton.zip.
vmmiguel said:
Excelent Rom very good accuracy of battery, but usb adb is not working
Click to expand...
Click to collapse
USB is working for me (09/29)
For testing I changed my wlan SSID to visible on my wlan router and a second later, wlan is connected. Setting it back to unvisible drops the connection. So I think its's a bug in 09/29 LOS preview.
Gesendet von meinem Moto X4 mit Tapatalk
Just got around to trying the FM Radio app, and it is not working for me - working for anyone else? I did not check if it worked on 15.1...
jhedfors said:
Just got around to trying the FM Radio app, and it is not working for me - working for anyone else? I did not check if it worked on 15.1...
Click to expand...
Click to collapse
I'm trying too, does not work
FM not working here also... build from 21.09. 2018. - Don't want to upgrade to 2909, waiting for October build, September builds look obsolete now
Demoniackers said:
Rom Pixel Experience unofficial TREBLE Android 9 ARM 64 A/AB (GSI) Working (TRY IT)
...
Running almost everything, in Moto x4
-Magisk, modules, Volte, bluetooth.
I have not tried, NFC, Hotspot
Bugs: Headphone Jack, Second camera, One Button (fingerprint gestures) It is not deactivated
Could you solve the errors?
Click to expand...
Click to collapse
Wrong thread/forum.
Edit: it is VERY bad form to spam all the different threads that you have posted to. If you annoy people, they are less likely to want to help you.
PLEASE HELP!
Unfortunately I do not know how to report error logs but I will describe my issue the best I can.
I am on a moto x4. XT1900-1, Android One edition. Bootloader Unlocked.
I followed the steps to a "T". Everything went smooth with rom install but I noticed a couple things. When running the flash_all.bat file, everything but flashing the modem completes successfully. It gives a failed message.
Code:
PS C:\platform-tools\firmware> .\fastboot flash modem_a modem.img
Sending 'modem_a' (112640 KB) OKAY [ 2.806s]
Writing 'modem_a' (bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 2.830s
It does this for modem_a and modem_b.
When I boot to bootloader(fastboot), it shows Baseband: <not found>
I haven't finished setup to see if I get cellular service. My guess is NO. Can you please help? Why would it be failing to flash the modem. I am trying the 8.1 firmware for Project Fi.
Thank you.
reedc83 said:
PLEASE HELP!
Unfortunately I do not know how to report error logs but I will describe my issue the best I can.
I am on a moto x4. XT1900-1, Android One edition. Bootloader Unlocked.
I followed the steps to a "T". Everything went smooth with rom install but I noticed a couple things. When running the flash_all.bat file, everything but flashing the modem completes successfully. It gives a failed message.
Code:
PS C:\platform-tools\firmware> .\fastboot flash modem_a modem.img
Sending 'modem_a' (112640 KB) OKAY [ 2.806s]
Writing 'modem_a' (bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 2.830s
It does this for modem_a and modem_b.
When I boot to bootloader(fastboot), it shows Baseband: <not found>
I haven't finished setup to see if I get cellular service. My guess is NO. Can you please help? Why would it be failing to flash the modem. I am trying the 8.1 firmware for Project Fi.
Thank you.
Click to expand...
Click to collapse
I once did a quick Google search on this issue as I too faced this problem. It is safe to ignore. Allow me to explain:
This is safe to ignore. All it means is that your device already has a new firmware at that particular base. I, personally, originally used, for my device, XT1900-1 Android 8.1 - courtesy @ptn107 https://www.androidfilehost.com/?fid=890278863836292604 and the first time I used it (coming from STOCK) everything flashed without any issues. A few updates later and if I attempt to use it again, it proceeds to flash everything and it skips (soft fails) on 1 point while proceeding to do everything else. This is because, on that particular point, I likely have a newer firmware.
You should be able to proceed as normal and safely ignore that small error.
MotoX4 said:
I once did a quick Google search on this issue as I too faced this problem. It is safe to ignore. Allow me to explain:
This is safe to ignore. All it means is that your device already has a new firmware at that particular base. I, personally, originally used, for my device, XT1900-1 Android 8.1 - courtesy @ptn107 https://www.androidfilehost.com/?fid=890278863836292604 and the first time I used it (coming from STOCK) everything flashed without any issues. A few updates later and if I attempt to use it again, it proceeds to flash everything and it skips (soft fails) on 1 point while proceeding to do everything else. This is because, on that particular point, I likely have a newer firmware.
You should be able to proceed as normal and safely ignore that small error.
Click to expand...
Click to collapse
Thank you for the information! I was able to proceed and most things seem to work fine.
I noticed a couple bugs to report so far.
- External SD not available.
- Project Fi will not get LTE on US Cellular or Sprint.
- Messages app will not allow dark mode. Option is there but it does nothing. (I noticed this in the latest official build of LOS 15.1 as well. 20181002 build of 15.1 worked fine.)(I did install OGAPPS so this may be my fault.)
- Settings > Display > Color? does nothing. On LOS 15.1, I could switch it to be more saturated. I put a question mark because I am back on stock at the moment and don't remember exactly what the color option was called.
Other than that I was loving the smoothness of the ROM. I want to go back but have a hard time living without my project fi working as I live in a remote location and drive back-roads and need for my service to work across carriers.
Question, do we need to install any of the stuff found on the GSI version like the FBE_Disable etc? I don't know what GSI stands for or how that differs from this. Sorry for the noob question.
Thank you so much for the OP and sharing this. Really hope to see an October build soon that address some of the bugs.
reedc83 said:
Thank you for the information! I was able to proceed and most things seem to work fine.
I noticed a couple bugs to report so far.
- External SD not available.
- Project Fi will not get LTE on US Cellular or Sprint.
- Messages app will not allow dark mode. Option is there but it does nothing. (I noticed this in the latest official build of LOS 15.1 as well. 20181002 build of 15.1 worked fine.)(I did install OGAPPS so this may be my fault.)
- Settings > Display > Color? does nothing. On LOS 15.1, I could switch it to be more saturated. I put a question mark because I am back on stock at the moment and don't remember exactly what the color option was called.
Other than that I was loving the smoothness of the ROM. I want to go back but have a hard time living without my project fi working as I live in a remote location and drive back-roads and need for my service to work across carriers.
Question, do we need to install any of the stuff found on the GSI version like the FBE_Disable etc? I don't know what GSI stands for or how that differs from this. Sorry for the noob question.
Thank you so much for the OP and sharing this. Really hope to see an October build soon that address some of the bugs.
Click to expand...
Click to collapse
Here the external SD works as portable storage with ou a problem.
The LTE is a known problem.
I don't know about the dark mode from message app.
In the stock rom you need to deactivate night mode to change the color, in Los 16 you change it at Live Display.
Android4Lumia - Android for Lumia 52x, 620 and 720Your warranty is now void. We are 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 the features included in these ROMs before flashing anything. YOU are choosing to make these modifications on your own, and if you point the finger at us for messing up your device, we will laugh at you.
Unofficial LineageOS 13/14.1 builds for Lumia 52x, 620, and 720
Only the Lumia 520, 521, 525, 526, 620, 720, and 720T are supported for now. There are plans to support other Qualcomm Snapdragon S4-based Lumias as well, though we cannot certainly promise anything.
Do not install this ROM on devices with a Samsung eMMC (flash memory chip)! These chips are known for getting either partially or fully write protected when you do this kind of stuff. While you still *can*, there's an high chance the eMMC will go write protected either during the process or even after. If you still chose to take the risk and your device is dead, don't blame it on us, this warning here and the one on the video are there for a reason!
Official website (For ROM and TWRP downloads): https://android4lumia.github.io/
OneDrive Link (For YouTube tutorial): https://1drv.ms/f/s!Atz2q1RD1cGL7nNWgZnXNjNiyu9f
To install Android on your Lumia, follow this video guide by sjrmac: https://youtu.be/_OW88UTTDug
Be sure to carefully follow all of the instructions or you may/will brick your device.
What works and what doesn't:
Wi-Fi works
Bluetooth works
RIL (SIM Card, Calls, Messages, Data etc.) doesn't work yet
Accelerometer (Rotation) doesn't work yet
Proximity and Light sensors don't work for me
Audio over headphone jack does not work for me
Camera does not work yet
Only official digitizer is supported. If you have an unofficial digitizer, you can try this kernel by TBM 13
For some people SD Cards don't work
You can install GApps, but keep in mind this will make your device very slow. Installing GApps is only recommended on Lumia 525 and 526, since these have 1 GB of RAM.
Do not install this software on your daily devices, because it is not 100% stable at the moment. Perhaps, depending on the device, there is a lot of lag and there are some important things that do not work.
To go back to Windows Phone, follow this guide, which you can also find in the website.
If you have not made a backup, you cannot go back to Windows Phone because every device is unique. Also, DO NOT share your backup with anyone, because by doing so you're giving private data such as IMEI away!
XDA:DevDB Information
Android4Lumia, ROM for the Nokia Lumia 520
Contributors
SuperLolMine, sjrmac, feherneoh, coherixmatts, banmeifyouwant, kholk, m11kkaa, PecanCM, thinhx2, trashmaster76
Source Code: https://github.com/Android4Lumia
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: WPInternals Bootloader Unlock, LK bootloader
Based On: LineageOS
Version Information
Status: Beta
Created 2019-10-17
Last Updated 2020-06-06
thanks, It worked. How do I use swap ram?( My phone only have 348Mb of Total RAM/326Mb in use). I used TBM13 kernel.
clgt said:
thanks, It worked. How do I use swap ram?( My phone only have 348Mb of Total RAM/326Mb in use). I used TBM13 kernel.
Click to expand...
Click to collapse
What ROM did you flash? LOS 13 or 14.1? As far as i know, LOS 13 only detects 359 MB of RAM, while LOS 14.1 detects more free ram so you might want to try flashing that.
clgt said:
thanks, It worked. How do I use swap ram?( My phone only have 348Mb of Total RAM/326Mb in use). I used TBM13 kernel.
Click to expand...
Click to collapse
SWAP RAM is already enabled by default. You don't need to do anything.
Nokia Lumia 630
Anybody tried this on the 630?
SuperLolMine said:
Android4Lumia - Android for Lumia 52x, 620 and 720Your warranty is now void. We are 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 the features included in these ROMs before flashing anything. YOU are choosing to make these modifications on your own, and if you point the finger at us for messing up your device, we will laugh at you.
Unofficial LineageOS 13/14.1 builds for Lumia 52x, 620, and 720
Only the Lumia 520, 521, 525, 526, 620, 720, and 720T are supported for now. There are plans to support other Qualcomm Snapdragon S4-based Lumias as well, though we cannot certainly promise anything.
Official website (For ROM and TWRP downloads): https://android4lumia.github.io/
OneDrive Link (For YouTube tutorial): https://1drv.ms/f/s!Atz2q1RD1cGL7nNWgZnXNjNiyu9f
To install Android on your Lumia, follow this video guide by sjrmac: https://youtu.be/_OW88UTTDug
Be sure to carefully follow all of the instructions or you may/will brick your device.
What works and what doesn't:
Wi-Fi works
Bluetooth works
RIL (SIM Card, Calls, Messages, Data etc.) doesn't work yet
Accelerometer (Rotation) doesn't work yet
Proximity and Light sensors don't work for me
Audio over headphone jack does not work for me
Camera does not work yet
Only official digitizer is supported. If you have an unofficial digitizer, you can try this kernel by TBM 13
For some people SD Cards don't work
You can install GApps, but keep in mind this will make your device very slow. Installing GApps is only recommended on Lumia 525 and 526, since these have 1 GB of RAM.
Do not install this software on your daily devices, because it is not 100% stable at the moment. Perhaps, depending on the device, there is a lot of lag and there are some important things that do not work.
To go back to Windows Phone, follow this guide, which you can also find in the website.
If you have not made a backup, you cannot go back to Windows Phone because every device is unique. Also, DO NOT share your backup with anyone, because by doing so you're giving private data such as IMEI away!
XDA:DevDB Information
Android4Lumia, ROM for the Nokia Lumia 520
Contributors
SuperLolMine, sjrmac, feherneoh, coherixmatts, banmeifyouwant, kholk, m11kkaa, PecanCM, thinhx2, trashmaster76
Source Code: https://github.com/Android4Lumia
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: WPInternals Bootloader Unlock, LK bootloader
Based On: LineageOS
Version Information
Status: Beta
Created 2019-10-17
Last Updated 2019-10-19
Click to expand...
Click to collapse
Hi Guys, doing some research, I found that, if you want your device to use the full RAM, you must recompile the kernel with ENABLE_HIGHMEM=yes option (because of the architecture of memory allocation in ARM and x86 systems).
I'm not good compiling and making linux kernels, but it wold be wonderfull if some of you try it to see if all RAM begin usable.
You are all making precious work on this proyect!
FredPuMa said:
Hi Guys, doing some research, I found that, if you want your device to use the full RAM, you must recompile the kernel with ENABLE_HIGHMEM=yes option (because of the architecture of memory allocation in ARM and x86 systems).
I'm not good compiling and making linux kernels, but it wold be wonderfull if some of you try it to see if all RAM begin usable.
You are all making precious work on this proyect!
Click to expand...
Click to collapse
If I'm not wrong, that flag is only used in devices that have a lot of RAM (even more than 2 GB)
TBM 13 said:
If I'm not wrong, that flag is only used in devices that have a lot of RAM (even more than 2 GB)
Click to expand...
Click to collapse
Well that's true, but is not all the true. That flag was "popular" in systems with memory >2GB because it let users to access memory pages originally reserved for the kernel (around 1 of 3 of the memory size, at least it says kernel.org), letting in this way take advantage of using more than the traditional 2GB that a i386 system can access.
However this has a processing cost, because the system has to liberate HighMem pages copying them to "another place" (not pretty sure if it occurs to swap space), take the new pages, processing them, an make the work back to have the original pages in place. So, in escence, disable access to HighMem, make the system faster and cheaper in cost of processing, but don't let you use full phisical memory, wich means less parallels aplications in memory.
Would be really intersting testing this in limited systems like Lumia, obviously this will have an effect on battery duration (more processing, more energy used), but if its not too drastic, will have the benefict of running more apps or bigger apps as well.
I'm still trying to learn how to recompile the kernel, but it's not my speciality... but if I can get it on, I'll be more than happy to let you know and share for testing the reconfigured kernel.
Meanwhile if someoane has success on it, would be great to know the experience.
bwilder said:
Anybody tried this on the 630?
Click to expand...
Click to collapse
The Lumia 630 is not supported, only 52x, 620, 720 and 720T.
I want to know how to install Sim (Etisalat) and how to fix cellular network connections?
thanks for your time
ahmedadelzayed said:
I want to know how to install Sim (Etisalat) and how to fix cellular network connections?
thanks for your time
Click to expand...
Click to collapse
You can't do that.
working fine with lumia 720
bwilder said:
Anybody tried this on the 630?
Click to expand...
Click to collapse
hey thanks ..i got it working for lumia720.
except for camera its in good state.
trying to install 1 G-app but its not able to add any google account to the device.
hence getting error ==no google account attached to this device===
any suggestion...
Build environment
Guys,
I have been able to make lineage13 is work in lumia720.great.
looking for setting up a build environment for lineosage13 .. locally .have downloaded code on Ubuntu but not sure about the which version of android sdk to use?
Regards
mhatreudu said:
Guys,
I have been able to make lineage13 is work in lumia720.great.
looking for setting up a build environment for lineosage13 .. locally .have downloaded code on Ubuntu but not sure about the which version of android sdk to use?
Regards
Click to expand...
Click to collapse
If you want to build AOSP/LOS, You don't need Android SDK. I suggest you to search for a build guide here in XDA
I was trying to install A4L even while my phone is showed in WInternals as SAMSUNG, not HYNIX because it's kind a useless without internet but after unlocking bootloader and trying to connect phone in mass storage mode i don't see it as "MainOS" in windows. Everything looks just like before i unlocked bootloader. Lumia 520.
siweq86 said:
I was trying to install A4L even while my phone is showed in WInternals as SAMSUNG, not HYNIX because it's kind a useless without internet but after unlocking bootloader and trying to connect phone in mass storage mode i don't see it as "MainOS" in windows. Everything looks just like before i unlocked bootloader. Lumia 520.
Click to expand...
Click to collapse
If bootloader is unlocked successfully then it should show the MainOS properly.Try restarting with powerbutton + vol up or down as appropriate key pressed simultaneously.make sure battery is full.
mhatreudu said:
If bootloader is unlocked successfully then it should show the MainOS properly.Try restarting with powerbutton + vol up or down as appropriate key pressed simultaneously.make sure battery is full.
Click to expand...
Click to collapse
It doesn't help. Tried several times.
siweq86 said:
It doesn't help. Tried several times.
Click to expand...
Click to collapse
the correction is power button+camera button,after the mobile vibrate release power button and hold on the camera button for approximately 4 secs.
worked for me and surely will work for you too.
mhatreudu said:
the correction is power button+camera button,after the mobile vibrate release power button and hold on the camera button for approximately 4 secs.
worked for me and surely will work for you too.
Click to expand...
Click to collapse
Doesn't work for me. When i press power + camera phone is booting but when i release camera button phone is turning off and i have to remove battery to start it again. Maybe it's because i have "Samsung" not "Hynix" in Windows Internals
hello
im trying to install os on 520
but in installing progress with side load, installation terminated at 47%
any idea why?