Database Users

[ROM] Unofficial CyanogenMod 9 [BLECM9 0.02]

Current status: CM10.1 in the works and this version will not be updated.
Got started with the project in January, I'm now ready to present you my first custom ROM (and kernel) - BLECM9!
First of all - BACKUP! This is not stable for everyday use just yet.
It also includes my own kernel, based on the latest CAF source code (ics_chocolate). The kernel gets frequent updates from CAF and me. Kernel version is 3.0.8. It's not as stable in the beginning but a better choice in the long term.
It won't include Google Apps, you need to manually install gapps package, as any other CM rom is by default.
Prequisites
U8800 upgraded to 2.3
ClockworkMod Recovery v5.5.0.4, not tested in v5.0.2.7
Instructions for Installing
Download the latest version of BLECM9 (Downloads below).
Copy the package to your internal/external SD card.
Reboot to recovery.
Flash the update package.
Optional: Install Gapps package (Downloads below).
Reboot and wait. The first boot takes around 2 minutes.
Downloads
My Google Code Page
Google Apps @ goo.im
Additional Notes
Report issues.
Changelog.
No, this won't work on U8800-51 or U8800Pro.
Atmel TS users, 0.02 will not work for you. I am establishing a new driver, to make the driver standard. Please standby as this is my top priority.
Everybody, send me logs if something does not work. This kernel is under heavy development. On computer with ADB set up: "adb shell dmesg > dmesg.log" and send the dmesg.log
Major Bugs
No Atmel TS support.
RIL issues (does not detect all SIMs)
NT35510 seems to have issues when turning on the screen (confirm?)
Unstable backlight on low values.
Wifi MAC address is 00:11:22:33:44:55
No Camera.
No Bluetooth.
No FM radio.
No audio (except ringtone/alarm)
Sometimes glitchy hardware acceleration.
No sensors.
More...
Credits: Huge thanks to dzo - without the proprietary blobs from him, this would've not been possible.
This is not just a work of mine, recently another developer joined the process and we are working together.
Collaborators: asm19
Feel free to contact me and also - contribute! Links for the source code is up on my GitHub (signature).
Follow my Twitter to see my development progress.

awesome. lets try
edit: when i try to write wifi password... see attachement. i can still write password, but i can't see what i am writing. everything works good in messeges
2nd edit: common cm problem... error while searching for network

Thanks for sharing.Looks good.

Been waiting for this. I will try it asap. I'm sure it will be get better day by day. Many thanks.

First of all Thank you!
First Impressions:
Touchscreen feels really responsive.
Rom feels very fast too.
Wifi is working good.
Bugs that I've found:
Screen flickering (unstable backlight)
Can't mount SDCard.
RIL isn't working on my u8800.
Overall it looks very promising!
Logs attached.

brdnacer said:
awesome. lets try
edit: when i try to write wifi password... see attachement. i can still write password, but i can't see what i am writing. everything works good in messeges
Click to expand...
Click to collapse
Yes, It's related to HW acceleration, causing some UI glitches.

Have been waiting for this for a long time, even if can't even use it because of Amtel TS.
Keep up with this awesome work

Thanks for this!
I'm using b518 and my phone is multibooting.My phone has recovery made by VICTOR TEAM (genokolar) .This ROM can be a problem for me in terms of Multiboot?Because you writed this in changelog;
New Partition Table.
Click to expand...
Click to collapse
Thank you in advance for the answer to my question!
Best regards...

Great! Been waiting for CM9 a long time ago too... Blefish, you should post some rules as to what we should and how to post in this thread, maybe instructions on how to post specific logs and what kind of info you need. The rest of the discussion should be posted in the general section. I would really hate for this thread to become a mess like Aurora's...
Sent from my U8800

I flashed 0.02, touchscreen didn't work. Then flashed Atmel-test2, touchscreen still doesn't work. Also phone reboots randomly.

I suggest to all of you interested helping Blefish, follow him on Twitter.
For those who tried Atmel-test-2-signed.zip
Blefish @ Twitter said:
Can you try doing in Terminal: "cat /devices/i2c-0/0-004a/input/input1" Do you get any output when touching?
Click to expand...
Click to collapse

forumber2 said:
Thanks for this!
I'm using b518 and my phone is multibooting.My phone has recovery made by VICTOR TEAM (genokolar) .This ROM can be a problem for me in terms of Multiboot?Because you writed this in changelog;
Thank you in advance for the answer to my question!
Best regards...
Click to expand...
Click to collapse
No changes done yet, it works like any other ROM right now.

Blefish said:
No changes done yet, it works like any other ROM right now.
Click to expand...
Click to collapse
Thanks for your answer.
I have one more question.Can i use your bootloader with multibooting?

I will test this after I have unbricked my galaxy tab (I don't want 2 problems same time)
Sent from my U8800 using Tapatalk 2

Is a good iniciative is a belfish source code?

Thanks for the feedback.
I am currently very busy in real life, exams are coming up too. I'll see if I can release another version sometime soon, to get the base working properly.

@Belfish don´t u have stoped de dev of cm9?
---------- Post added at 05:56 PM ---------- Previous post was at 05:53 PM ----------
Blefish said:
Thanks for the feedback.
I am currently very busy in real life, exams are coming up too. I'll see if I can release another version sometime soon, to get the base working properly.
Click to expand...
Click to collapse
Can u use libs from aurora?

anjo88 said:
@Belfish don´t u have stoped de dev of cm9?
Click to expand...
Click to collapse
Noo, I'm not going to stop, just saying I am bit busy so development might not be as fast in the coming 2-3 weeks.

Blefish said:
Noo, I'm not going to stop, just saying I am bit busy so development might not be as fast in the coming 2-3 weeks.
Click to expand...
Click to collapse
ok we wait bood luck for the exames is good if u have some help! Please put a donate button in thread so we can donate u a bear u diserv!

Another bug: it does not recognize my SIM card (TMN)
Also, LOTS of graphical bugs.

Unofficial announcement of CM10.1/10.2

Latest Downloads
CM10.1 http://d-h.st/i3V
CM10.2 https://drive.google.com/file/d/0B1V_hMyelDz0Rm1nenlqT2JKWkE/edit?usp=sharing AS OF 21.11.2013
UNOFFICIAL FAQ FOR CM10.1/10.2
DOWNLOAD AND INSTALLATION
Q: Where’s the download?A: The initial FXP release had an incorrect kernel – you can download a working version of ROM from here. http://d-h.st/TPT
This ROM has since been updated a download can be located here. http://d-h.st/i3V
If you wish to try a CM10.2 (that’s Jelly Bean 4.3 – have Sony actually released a 4.3 ROM yet?) one can be downloaded from the link above.You can also download the correct version of GAPPS for Jelly Bean 4.3 here. http://brintaylor.info/Android/CM/gapps/
For the CM10.2 build you should use this link to report bugs. https://docs.google.com/forms/d/185s...9UINQ/viewform
Uberlaggydarwin plans to take a 'light touch' approach to support via XDA, so don't necessarily expect an answer to a query if you post in this thread
It seems like FXP have delayed releasing for our device for now, but information about CM builds that are being actively supported and developed can be found in this thread for now.
Q: How do I install?
A: You need an unlocked bootloader and an installed recovery. BACK UP your current ROM to your external SD card. Put the ROM and GAPPS on your external SD card. Boot into your recovery, do the necessary wipes, flash the ROM, flash GAPPS, reboot, victory. Disclaimer: if it breaks your phone, it’s your fault.
Q: Do I need to install the supplied kernel before installing the ROM?
A: No, unlike older xperia models CWM is able to flash both the kernel and the ROM at the same time. There is no need to use fastboot or flashtools to flash the kernel first, just a working recovery and an unlocked bootloader on your phone.
Q: Can I use another kernel instead?
A: No, for now only the supplied kernel will work.
Q: I’ve installed the ROM but can’t find the play store?
A: Immediately after installing the ROM you should install the 4.2.2 version of GAPPS (Google Apps) – this installs the play store and several other applications that Google regard as essential to the Android experience. This can be found here – http://goo.im/gapps/gapps-jb-20130812-signed.zip
Q: How do I update to the latest version of the ROM?
A: Once you’ve downloaded the latest version to your SD card, boot into recovery. No need to wipe your data, though you probably should wipe cache and dalvik cache (I don’t know whether this is done automatically as part of the installation but it can’t do any harm). You don’t need to install GAPPS again as this is a firmware update, not a new installation.
However if you’re moving between versions i.e. 10.1 to 10.2 you should definitely do a factory reset – the ROM may well work fine without a data wipe, but it may not and any problems might not be immediately noticeable (making bug tracking difficult). I would advise you NOT to report bugs if you’ve moved between android versions without a factory reset.
Q: When will they release a version that works on a locked bootloader?
A: Never. Some the features of the ROM simply won’t work very well/at all on a stock kernel. If you are rooted you can simulate some of the features with apps and mods though.
POST-INSTALLATION QUESTIONS
Q: I’ve installed the ROM – I can use Titanium Backup to reinstall all my apps right?
A: Yes and no. They may work fine, they might not – you are better off letting Google’s back up service restore all your apps. If you restore an app using Titanium or similar software and it’s buggy, there’s no point reporting it – re-install the app instead, perhaps even the ROM.
Q: 4G isn’t working – what do I do?
A: It’s not enabled by default on CM10.1 so you must do the following.
Go to the dialpad/phone.
Dial in the this number: *#*#4636#*#* (This will bring up "Phone info").
Tap WCDMA from under "Set preferred network type".
Select "LTE/GSM/CDMA auto (PRL)".
The 4G LTE network should now be activated.
Q:Where’s USB mass storage?
A: After ICS Google stopped including it in their Android builds, as such mass storage mode is not a feature that was kept by CM for Jelly Bean. Individual manufacturers do what they want though, which is why Sony, Samsung and others still have it. Skilled modders may be able to add to ROMS based on this development, I reckon they might be able to patch this one to include it too
Q: This ROM is buggy as hell and drains my battery – how do I let the developers know?
A: Logcat and/or a kernel log - or it didn’t happen for bugs.
Better battery stats for battery drain.
There are lots of guides out there showing you how to take logs and how to record battery stats.
Anecdote – I activated Google+ yesterday as I like the auto-photo upload feature but wakelock detector revealed it was killing my battery (I think it’s dodgy on stock too). The choice was the app or the ROM, I chose the ROM.
Q: After installation something random doesn’t work – what do I do?
A: Check the thread to see if other users have mentioned the issue and to see if the developer has posted a solution. Also, you’re on XDA, you’re an advanced user, you have unlocked your bootloader, thrown out your warranty and accepted the consequences. So please try to resolve the issue yourself. In general if you are having a problem and no one else is, it will be a problem with your phone/download/installation.
Phone - obviously a hardware fault can't be foreseen by the developer and have you unlocked your bootloader!
Download - Most downloads are fine. But I've flashed enough ROMS to know that sometimes a file gets corrupted and sometimes they say they are complete when they are not. Sometimes I've been careless and clicked on the wrong download, sometimes the website hosting the site is haveing a a bad day, sometimes the developer puts the download in the wrong place too The first things to check are the name and size of the file - if these tally you're probably fine to install. If you want to be extra cautious you can check the MD5 hash to see if your download matches. Sometimes the file gets corrupted on upload - nothing anyone can do about that...
Installation - (Please back up your orignal ROM). Typically you'll be installing this ROM using a recovery from another ROM/kernel/MOD - so if you have problems installing , it might be that you have a bad recovery.
The wipes really need to be done to ensure the smooth running of your phone, but as you've backed up, the 15 seconds you spend properly wiping should not be much of a chore.
If you're one of the first downloaders, I guess there is some merit in saying you couldn't install, but if it's been out for a while and there are loads of posts saying 'what a great ROM' there's little point posting 'won't install'. Describe exactly what you've done and someone might help.
Bear in mind there are apps/hardware that the developers of this ROM won’t have heard of/care about - so if something doesn’t work properly on your phone it could be for numerous reasons. Either way, this may be something you have to live with. Alternatively, if the app is essential to you, you’ll have to return to a backup.
Remember this ROM is in development, there are no promises of perfection and no one is forcing you to use it. However, the right kind of feedback is always welcomed by the developers and may be acted on – the wrong kind will often be ignored.
Q: What does a perfect bug report look like?
A: Go here. http://forum.xda-developers.com/showpost.php?p=46935640&postcount=313
Q: What are the known bugs?
A: FM radio doesn’t work.
A: Attempts to offline charge cause the phone to boot.
A: 4G activation is not remembered between boots for CM10.1.
A: For 10.2 there is a known battery drain issue related to WiFi. See the solution here. http://forum.xda-developers.com/showpost.php?p=46923723&postcount=301
The following issues have been reported by some users, but others say it doesn’t affect them. They are regarded as hardware issues – anecdotal ‘me too’ posts will be ignored. However, supply a log and your phone’s date of manufacture and the developer may look into it (this might help you prove that your phone is faulty, so it’s a worthwhile exercise).
Erratic touch screen response.
Reading external SD Card in recovery and in use.
As others have said this is possibly the most stable first CM build they’ve encountered and I agree – it’s definitely suitable for daily use. I've been using it from release and haven't had a single reboot/app crash or freeze.

http://uploaded.net/f/q3au96
CM 10.1 released for huashan

Its cm for our phone right?!??
Sent from my ZTE Blade G using xda app-developers app

Thanks for sharing. I saw yesterday in the changelog that both 10.1 and 10.2 where announced on FXP 242 (10.1 in beta and 10.2 in alpha), but I can't find the 10.2 download anywhere.
Maybe they don't publish public download links for alpha versions ?

Parkside said:
...no announcements, I can't keep it to myself. You'd do the same right?
Click to expand...
Click to collapse
Its safe to download huanshan cm file for our phone.(know that huanshan is code name for our phone)????
Sent from my ZTE Blade G using xda app-developers app

Yes take a look

karma123 said:
Yes take a look
Click to expand...
Click to collapse
Wooohooooo im so happy i cant wait to test itThanks to FXP team !
When i flash it im gonna make review wohoooooo
Sent from my ZTE Blade G using xda app-developers app
---------- Post added at 12:06 PM ---------- Previous post was at 11:58 AM ----------
karma123 said:
Yes take a look
Click to expand...
Click to collapse
Can you tell me what file to download??
Sent from my ZTE Blade G using xda app-developers app

Download this :- http://uploaded.net/file/7ntq0zp6/from/q3au96
Flashed and booted. Its nice. But some screen flickering while scrolling. Like in settings etc etc. But that can resolve with enable the " Disable Hardware Overlay" option from Developer Settings

What about performance ? Can you run antutu bench ? how much is free / used RAM ? etc.
thanks

Are mirrors allowed? Can somebody mirror this file? Im sorry but uploaded has failed me several times already...

mmm273 said:
What about performance ? Can you run antutu bench ? how much is free / used RAM ? etc.
thanks
Click to expand...
Click to collapse
Now only i flashed this. I dont have any apps installed. So performance is awsom now. Free RAM is 509 and used 333

ok, only for compare - what antutu score ? With stock ( fresh flash) i have 21 000...

Screen Flicker
Hi @Rajeev
I didn't experience screen flickering at ALL in ANY test builds so I find this really difficult to believe but I'm happy to take a detailed look at it ..
Log's plus video(so I can see what you mean) would be useful so I can get this possible ?issue? and if it is an issue then I'll get it resolved.
None whatsoever for me so this is a really weird issue....
Thanks

I have the flickering too ! And the phone often soft freezes. Seems like the app isnt updated anymore on screen. It can also be just the keyboard for example. Hiting recent tasks unfreezes it but systemui sometimes freezes until reboot.
Sent from my C5303 using xda app-developers app

uberlaggydarwin said:
Hi @Rajeev
I didn't experience screen flickering at ALL in ANY test builds so I find this really difficult to believe but I'm happy to take a detailed look at it ..
Log's plus video(so I can see what you mean) would be useful so I can get this possible ?issue? and if it is an issue then I'll get it resolved.
None whatsoever for me so this is a really weird issue....
Thanks
Click to expand...
Click to collapse
Hi Bro @uberlaggydarwin
Yes i am saying truth only.
1) While Scrolling in settings Its flickering like waves. But its not coming after Click the " Disable Hardware Overlay" Function.
2) When i press the Reboot option its rebooting but its rebooting like something weird in Screen..
3) Soft reboots happens multiple Times...
I know its a Beta release. I am not complaining . But answering ur question...

mmm273 said:
ok, only for compare - what antutu score ? With stock ( fresh flash) i have 21 000...
Click to expand...
Click to collapse
I'd like to see a screen of that score. Seems a bit too high. Sure you have the SP ?
You're using V4 ofcourse, my bad.

Bootloader
Just wondering if you are guys are using locked or unlocked bootloader? I'm locked with CWM and I'm wondering what the process would be of installing... (e.g. wiping /data...)

jakelooker said:
Just wondering if you are guys are using locked or unlocked bootloader? I'm locked with CWM and I'm wondering what the process would be of installing... (e.g. wiping /data...)
Click to expand...
Click to collapse
Hey, Make a backup, you need an unlocked bootloader for this. Then wipe all cache and data etc. then flash the rom on your phone

jakelooker said:
Just wondering if you are guys are using locked or unlocked bootloader? I'm locked with CWM and I'm wondering what the process would be of installing... (e.g. wiping /data...)
Click to expand...
Click to collapse
Well asfaik CM requires a custom kernel which can only be installed on a phone with unlocked bootloader. Hope ive helped.

Rajeev said:
Hi Bro @uberlaggydarwin
Yes i am saying truth only.
1) While Scrolling in settings Its flickering like waves. But its not coming after Click the " Disable Hardware Overlay" Function.
2) When i press the Reboot option its rebooting but its rebooting like something weird in Screen..
3) Soft reboots happens multiple Times...
I know its a Beta release. I am not complaining . But answering ur question...
Click to expand...
Click to collapse
LOG"S OR IT DIDN"T HAPPEN . I'm serious.
I'm downloading this release to test but I can't help much if you don't provide logs.
Are you sure its not auto-brightness being turned on as auto-brightness doesn't work very well in stock so the changes are probably more noticeable.
Reboots work perfectly fine for me..
On the recent test builds I haven't had a reboot issue but as you know the kernel is temporary so I'll redo it when 4.3 comes out....
WE NEED LOGS.

No longer needed (Admin pls. close)

No longer needed... Visit official thread by @LuK1337 : http://forum.xda-developers.com/moto-g-lte/orig-development/rom-cyanogenmod-13-0-t3245547
Please admin close this thread. Thank you.

No longer needed... Visit official thread by @LuK1337 : http://forum.xda-developers.com/moto-g-lte/orig-development/rom-cyanogenmod-13-0-t3245547

RIL is not working
Cameo164 said:
When you try it please tell if it works for you. And sorry that's my first thread .
Click to expand...
Click to collapse
I know you just sharing for the hype, but, at least on XT1078 (dual sim) RIL is not working, the system did not recognize a SIM card in any slot, don't know if it's because the dual sim stuff... The rest seems to behave just like you mentioned, so thanks for sharing anyway!!
Edit: By the way, I managed to install without Titan's Recovery... To be honest, when I tried to boot in titan's recovery my phone kind of bootlooped... So I decided to modify updater-script and change the match names to thea (XT1078), it installed flawless and booted just fine.

Okay that's sad to hear but I can't do much at the moment. But thank you for trying.
EDIT: Multi sim fixed in 07.11 build.

Where is the original thread ? I can't find it. You should give a link in the first post as it is not your ROM but thanks for sharing !

Mavireck said:
Where is the original thread ? I can't find it. You should give a link in the first post as it is not your ROM but thanks for sharing !
Click to expand...
Click to collapse
That's the problem. I can't find it too. I got the download link from the Moto WhatsApp Group.
EDIT: I found it. I will update the post.

I saw cyanogenmod so my post does relate to this thread...
so basically i unlocked my bootloader on my Moto G 2014 LTE, I rooted my phone and then installed and flashed using TWRP:
tk_gapps-stock-5.1.1-20151004-signed.zip
Full-CM-12-21-03-15-Bacon-modem-flashable.zip
Both successfully installed and flashed and then I rebooted the system as per the instructions and then my phone screen, instead of rebooting with cyanogen, it went black and wont turn on.
Please could someone tell me what I need to do to get it up an running, I have tried the following:
- holding down power and volume down button for two minutes whilst on charge
- leaving it on charge for 15 minutes and then repeating the above step
- I have plugged it into my computer and it has picked up that there is something plugged in, but my phone drive never shows up.
Thank you

why new thread if it is work of luk and luca?
mayurim said:
I saw cyanogenmod so my post does relate to this thread...
so basically i unlocked my bootloader on my Moto G 2014 LTE, I rooted my phone and then installed and flashed using TWRP:
tk_gapps-stock-5.1.1-20151004-signed.zip
Full-CM-12-21-03-15-Bacon-modem-flashable.zip
Both successfully installed and flashed and then I rebooted the system as per the instructions and then my phone screen, instead of rebooting with cyanogen, it went black and wont turn on.
Please could someone tell me what I need to do to get it up an running, I have tried the following:
- holding down power and volume down button for two minutes whilst on charge
- leaving it on charge for 15 minutes and then repeating the above step
- I have plugged it into my computer and it has picked up that there is something plugged in, but my phone drive never shows up.
Thank you
Click to expand...
Click to collapse
Use this guide: https://wiki.cyanogenmod.org/w/Install_CM_for_thea

RolanDroid said:
why new thread if it is work of luk and luca ?
Click to expand...
Click to collapse
Because I found it in the comments from the CM12.1 Builds for our devices and I thought I could share their great work and show the other people what they already did because there is no official thread at the moment. And I wrote in my first post that it's their work.

Anyone tested this on XT1069 Titan?

Ace2213 said:
Anyone tested this on XT1069 Titan?
Click to expand...
Click to collapse
For titan it would be this file : https://s.basketbuild.com/filedl/de...M13/titan/cm-13-20151021-UNOFFICIAL-titan.zip
But because XT1069 is a dual sim phone RIL (Calls, SMS, Data) will not work. So I wouldn't recommend you to install it. I'm sure it will be fixed soon.

I use it as a tablet, so I don't mind lack of dual Sim support
---------- Post added at 02:29 AM ---------- Previous post was at 02:21 AM ----------
Does everything else work though?

Ace2213 said:
I use it as a tablet, so I don't mind lack of dual Sim support
---------- Post added at 02:29 AM ---------- Previous post was at 02:21 AM ----------
Does everything else work though?
Click to expand...
Click to collapse
Everything works except the things in What's not working in Post 1. The biggest bugs at the moment are that you can't select an other language than english and that Screenrotation is sometimes buggy and you have to restart the phone to get it working again.

I only use English so that's not an issue. I had the screen rotate bug in "stable" roms on two phones. Does it affect games and movies (auto rotated apps) or only switching rotation on and off?

Ace2213 said:
I only use English so that's not an issue. I had the screen rotate bug in "stable" roms on two phones. Does it affect games and movies (auto rotated apps) or only switching rotation on and off?
Click to expand...
Click to collapse
No it doesn't affect games and apps with only one orientation available. But I had to download an app called "rotation control" to rotate my screen when I'm in apps for example browser or apps.

How is this CyanogenMod? This is AOSP with the CM launcher and wallpaper, that's it. And what are these weird search and browser apps?
This isn't CyanogenMod. There is not even advanced reboot menu. This is 100% stock. And no xposed of course. I'm going back to RR.

Ace2213 said:
How is this CyanogenMod? This is AOSP with the CM launcher and wallpaper, that's it. And what are these weird search and browser apps?
This isn't CyanogenMod. There is not even advanced reboot menu. This is 100% stock. And no xposed of course. I'm going back to RR.
Click to expand...
Click to collapse
It is cyanogenmod, early version of it to be exact. They just didn't merge their things yet.

Ace2213 said:
How is this CyanogenMod? This is AOSP with the CM launcher and wallpaper, that's it. And what are these weird search and browser apps?
This isn't CyanogenMod. There is not even advanced reboot menu. This is 100% stock. And no xposed of course. I'm going back to RR.
Click to expand...
Click to collapse
This is only for testing and development purposes my friend, it is not even a nightly!
It is just an early build and a really good one!

My bad. It is a great build. The only issue is gapps. All the ones I found for 6.0 keep FCing randomly and having permissions issues, even when all permissions are allowed

I had the same problem Ace2213, so I've reverted back to 12.1 for now and wait for a proper Nightly of 13.

Ubuntu Touch for OPO

https://devices.ubports.com/#/bacon
Apparently stable has been released, unfortunately i don't have the means to test it yet.
Anyone tried out the release? Cannot find proper material on the functionality and or features.
Site claims it's good for daily use, therefore if anyone can test it and report, would be awesome.
Edit. Build does not work daily

How is this a daily driver when the release clearly states GPS & Camera still doesnt work? ?

https://devices.ubports.com/#/
Here says :
Active devices are devices that are fully working as daily drivers, it requires to have wifi, call, sms, data, OTA, apparmor and sound to be working to be an "Active device".
Only bluetooth is not working according to the list on that website.

Camera and GPS "work" but still have major issues.
Extremely buggy. Not stable.

TapioH said:
https://devices.ubports.com/#/
Here says :
Active devices are devices that are fully working as daily drivers, it requires to have wifi, call, sms, data, OTA, apparmor and sound to be working to be an "Active device".
Only bluetooth is not working according to the list on that website.
Click to expand...
Click to collapse
Notice you didn't list camera or GPS on that list. 2 things still not completely working. If you click on the device it has a list of features in red and green on the next page.
Camera & GPS are in red but listed, meaning they work, but are very buggy. I've used these builds before man...you clearly haven't as you are asking someone to test it for you.
If you're idea of a "daily driver" is no Bluetooth & barely working camera/GPS you don't understand the meaning of "daily driver." From a technical standpoint all that is required for the Ubuntu dev page to be a daily driver is if everything works, not if everything works flawlessly...
I'm all for people testing this but its not good to convince people to install this on their phones with false pretenses.
*TO ALL AVERAGE USERS. FEEL FREE TO TRY, BUT THIS IS NOT A DAILY DRIVER. DO NOT LISTEN TO THIS GUY EXPECTING THIS TO FUNCTION LIKE A PERFECT ROM BUILD.

I've been using Ubuntu on my PC for years and I really want Ubuntu phone to carve up its share in the market. I installed Ubuntu Touch via multirom and it is barely an OS especially if you are coming from XDA and its riches. It was buggy, the camera didn't work and even if everything were to work flawless, you'll be still lacking the apps to make phone a bit smarter.

check the site just bluetooth is not working rest fine but cant install via multirom recovery v33b doesn't boots help how to do so

Dhairya said:
check the site just bluetooth is not working rest fine but cant install via multirom recovery v33b doesn't boots help how to do so
Click to expand...
Click to collapse
So you couldn't even get the OS to boot but here you are claiming how pretty much everything works? Lol

Dhairya said:
check the site just bluetooth is not working rest fine but cant install via multirom recovery v33b doesn't boots help how to do so
Click to expand...
Click to collapse
You have to install the Multirom-recovery from February manually, the lastest one doesn't work with Ubuntu Touch on the OPO. Also make sure to have everything ext4 formatted, had problems with f2fs and Multirom.
Once Ubuntu Touch is installed it's pretty stable and somewhat fast (not as fast as Android MM tho). But the lack (and quality) of apps really is a problem

StarStorm said:
You have to install the Multirom-recovery from February manually, the lastest one doesn't work with Ubuntu Touch on the OPO. Also make sure to have everything ext4 formatted, had problems with f2fs and Multirom.
Once Ubuntu Touch is installed it's pretty stable and somewhat fast (not as fast as Android MM tho). But the lack (and quality) of apps really is a problem
Click to expand...
Click to collapse
can u give me the link of it plz of recovery and secondly if download multi-rom apk its show by default v33b i tired installing v32j flashable but said Ubuntu wont work u need latest v33b if link can be der would be helpful !
---------- Post added at 08:14 PM ---------- Previous post was at 08:14 PM ----------
h11wiscan said:
So you couldn't even get the OS to boot but here you are claiming how pretty much everything works? Lol
Click to expand...
Click to collapse
check the site bro its has all your answers !

Thanks for the responses everyone. It appears people had more knowledge on the subject than me. So it's nowhere near "daily driver".
Keeping my hopes up for a fully functioning one though.

flashed latest stable v14 cannot make or receive calls sim gets detected network comes too for eg:- if i call from any other phone then its rings but doesnt shows on my phone

TapioH said:
Thanks for the responses everyone. It appears people had more knowledge on the subject than me. So it's nowhere near "daily driver".
Keeping my hopes up for a fully functioning one though.
Click to expand...
Click to collapse
You should edit your first post as a favor to the newer members who might try this under the false pretenses of your first post. :good:

Ubuntu Touch
I am excited I got Ubuntu touch and wifi working. If anyone wants the instructions, let me know.

hi can you give me the instructions, thank yhou

I think this page have everything you need https://devices.ubuntu-touch.io/installer, found it from https://forum.xda-developers.com/oneplus-one/general/ubuntu-touch-opo-t3433634
Please search before asking in a new thread. this consider spamming.

[WIP][DOWNLOADS] A new take on a graphical installer for LineageOS

Hello!
Usually I mainly consult this forum to get unofficial builds of LineageOS or look for support when occasionly something goes wrong. Some time ago I wondered, why it has to be so annoying to install LineageOS (or most of the other custom ROMs). There have been several attempts to create a graphical installer for LineageOS (most famously this one) and some installers for specific ROMs like calyxos. But support for devices is rather limited and hard to extend.
So I decided to give it a try myself and create a new attempt to build a graphical installer for alternative Android ROMs.
Repository: https://github.com/openandroidinstaller-dev/openandroidinstaller
Features:​- Graphical installer with instructions.
- onefile executable.
- adb, fastboot, heimdall and some drivers included.
- Works on Linux (mainly tested on Ubuntu 20.04), MacOS (not on ARM, M1, M2) and windows (you might need to install some drivers manually).
- some checks if the selected LineageOS image and recovery works for your device.
- Installation steps are based on config files to add support for new devices.
- written in python
Supported devices:​- Currently, the alpha version mainly supports Google, Samsung, Fairphone and Sony devices, but should be fairly easy to extend to other devices.
Alpha version release download:​https://github.com/openandroidinstaller-dev/openandroidinstaller/releases
How can you help?​All kinds of feedback are useful! Let me know what you think in this thread.
If you have a unused device that supports LineageOS, perhaps you could try out this tool and report your results in this thread! I bought a bunch of different android devices, but more testing on all kinds of devices is needed and very welcome! Also testing the tool on different platforms (windows, macos, etc.) would be super helpful.
Note that:
- It may screw up your device. No automatic restore process is implemented yet, so make sure to have some sort of recovery tool handy.
- When you report back, please include the version of the program you used (as identified in the Downloads section), along with your device.
- Read the repository's README for further details!
- This installer is not associated with official LineageOS.

Getting a new phone this week, will give it a shot

SigmundDroid said:
Getting a new phone this week, will give it a shot
Click to expand...
Click to collapse
Thanks a lot! I'm looking forward to your feedback!
What phone are you getting? I might be able to help you with support

FP3. Was hoping it'll arrive today... alas, didn't come, so probably I can check not before the weekend.

Great! I'll make sure, that there is support for the FairPhone 3 on the weekend, but note, that it hasn't been tested yet, since I don't have a FairPhone 3. So I'm super happy about any feedback I can get
If you have questions, let me know!

Devices that should work out of the box now:
VendorDevice NameCodeNameModelsStatusSamsungGalaxy A3 2017a3y17lteSM-A320FLtestedSamsungGalaxy A5 2016a5xelteSM-A510FtestedSamsungGalaxy S7herolteSM-G930FtestedSamsungGalaxy S9starlteunder developmentGooglePixel 3asargosargotestedSonyXperia ZyugaC6603testedSonyXperia Z3z3under developmentFairphoneFairphone 2FP2under developmentFairphoneFairphone 3FP3under developmentMotorolamoto g7 poweroceanunder development
In general, it should be pretty easy to use the tool for all kinds of Samsung, Pixel, Sony Xperia, Fairphone and Motorola devices. Let me know if you need help with your devices.

{
"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"
}
OK, it works with FP3! Awesome! Actually, that might become a nice little helper for flashing LOS!
Ran into some problems:
Had to OEM-unlock first. Could be little bit more elaborate (I usually forget to reboot the phone after that and authorize my PC, lol)
First 2 times it hang, only the console told me it looks for https://lineageosroms.com/fp3/ (not official, is it?)
Had to unlock with fastboot flashing unlock
That can be a big problem for beginners if you face it the first time
A little bit more feedback during flashing would be nice, console (and phone) showed more than the installer
Overall very good approach! Well, except for the lack of feedback (errors/progress from console). Is there any logging?
PS: Used it on Debian Bullseye with KDE.
PSPS: Perhaps an overview of the steps would fit in there as well (so one can see past, current and future steps)?

Awesome! Thanks for giving it a try!
Had to OEM-unlock first. Could be little bit more elaborate (I usually forget to reboot the phone after that and authorize my PC, lol)
Click to expand...
Click to collapse
Very good point!
First 2 times it hang, only the console told me it looks for https://lineageosroms.com/fp3/ (not official, is it?)
Click to expand...
Click to collapse
In the next release it will point to the official page. I wasn't aware that this page is not at all related to LOS and not so well perceived in the community as some of the devs pointed out to me. The check is done, to find out if there is an official release of LOS and then recommend the download. There might be a better way to guide users to find an appropriate image for their device, but that was simple.
Had to unlock with fastboot flashing unlock
That can be a big problem for beginners if you face it the first time
Click to expand...
Click to collapse
That was my bad... I didn't read the "unlock bootloader" instructions of the FP-support page carefully enough and stopped after part 1. This should be easy to address by updating the config. It will be fixed in the next release.
A little bit more feedback during flashing would be nice, console (and phone) showed more than the installer
Click to expand...
Click to collapse
That's very true! I'm trying to figure out, what kind of feedback is appropriate to keep people informed, but not scare them. A progress bar for flashing is in the making. Optimally, the installer can also show images of what should be going on on the phone. But that will mostly rely on community contributions for phones I don't own.
Thanks a lot for the detailed feedback! I will try to address most of them in the next release, especially more information and feedback for the user.
PS: Are you using the FP3 as your daily driver now, or would you be open to test the installer again in a few weeks or so?
PPS: I'm thinking about moving away from LOS recovery all together and only support TWRP since it allows for much more automation. What are your thought on that?

__sterby__ said:
official release of LOS
Click to expand...
Click to collapse
Would that link do it?
https://download.lineageos.org/FP3
__sterby__ said:
That was my bad... I didn't read the "unlock bootloader" instructions of the FP-support page carefully enough
Click to expand...
Click to collapse
Hmm, I vaguely remember the exact same thing happened to me as well at my first manual flashing. Don't other phones do that as well nowadays? I could swear the S5 i flashed 2 weeks ago did it also...
__sterby__ said:
what kind of feedback is appropriate to keep people informed, but not scare them
Click to expand...
Click to collapse
Hmm, I would certainly appreciate the "real" output as provided in console. Without it I wouldn't have really known what your installer is trying to do.
Putting some pictures wouldn't hurt but I really think that a "map" of steps is useful, too. Besides, one can see the whole progress at once (so far it's a somewhat nebulous process in my mind... and I always! tend to forget something).
__sterby__ said:
using the FP3 as your daily driver now
Click to expand...
Click to collapse
Nah, not yet... that's actually why I got this second phone, so can test stuff without killing off my daily driver (after some horrible experiences I am insisting to try a new phone/ROM for some weeks before I switch).
So, yes, keep it coming Your idea is awesome (and saves me some time as well).
__sterby__ said:
moving away from LOS recovery all together and only support TWRP
Click to expand...
Click to collapse
Awesome! A recovery without backup (like LOS) seems moot anyway (seems like a must have to me). Was thinking to switch already but wasn't sure about any implications (A/B vs TWRP, didn't fully grasped the A/B stuff yet)...
Uhm, rooting wouldn't be on your agenda, too? That is a thing still causing me trouble (I have to read up on it every single time).

SigmundDroid said:
Would that link do it?
https://download.lineageos.org/FP3
Click to expand...
Click to collapse
Yes And probably also to the relevant TWRP page soon.
SigmundDroid said:
Hmm, I vaguely remember the exact same thing happened to me as well at my first manual flashing. Don't other phones do that as well nowadays? I could swear the S5 i flashed 2 weeks ago did it also...
Click to expand...
Click to collapse
No, other phones also require this step. Since the fairphone 2 doesn't require it (as far as I know the bootloader is already unlocked), I assumed that could be similar for the Fairphone 3.
SigmundDroid said:
Hmm, I would certainly appreciate the "real" output as provided in console. Without it I wouldn't have really known what your installer is trying to do.
Click to expand...
Click to collapse
Thanks for the suggestion, I'm working on an "advanced output mode" that lets you see all the terminal input and output.
SigmundDroid said:
Putting some pictures wouldn't hurt but I really think that a "map" of steps is useful, too. Besides, one can see the whole progress at once (so far it's a somewhat nebulous process in my mind... and I always! tend to forget something).
Click to expand...
Click to collapse
yeah, I'm thinking about how to integrate this in a useful way. A bit more overview would be nice.
SigmundDroid said:
Nah, not yet... that's actually why I got this second phone, so can test stuff without killing off my daily driver (after some horrible experiences I am insisting to try a new phone/ROM for some weeks before I switch).
So, yes, keep it coming Your idea is awesome (and saves me some time as well).
Click to expand...
Click to collapse
Perfect! Thanks a lot, I'm already working on a new release and hopefully there will be much more automation and more user information (and a fully working config for the fairphone 3). I keep you updated!
SigmundDroid said:
Awesome! A recovery without backup (like LOS) seems moot anyway (seems like a must have to me). Was thinking to switch already but wasn't sure about any implications (A/B vs TWRP, didn't fully grasped the A/B stuff yet)...
Click to expand...
Click to collapse
So far, it works kind of okay with TWRP I would say, but I'm having weird issues on the Google Pixel with it and wasn't able to find anyone who might know anything about it. Using twrp commands in the adb shell seems to be not so common...
Either way, I would try to get away with just booting into TWRP, wiping and flashing from there. This is an approach that seems to work fine with A/B-partitioned phones as far as I can tell.
SigmundDroid said:
Uhm, rooting wouldn't be on your agenda, too? That is a thing still causing me trouble (I have to read up on it every single time).
Click to expand...
Click to collapse
It's not on the short-term agenda. But definitely something I'm thinking about. I should probably put a proper roadmap on github

Soooo, now there is a new alpha Release
Release Alpha release v.0.2.1 · openandroidinstaller-dev/openandroidinstaller
This is an alpha release of the OpenAndroidInstaller. Linux, MacOS and Windows are supported, but the testing is mainly done on under Ubuntu 20.04. Note, that currently there is no support for ARM-...
github.com
This time mainly visual improvements and more automation. This is mainly achieved by switching recovery support completely to TWRP (currently only booted, only flashed on samsung devices).
There is now an option to get advanced output, printing commands run and terminal output in the tool. This is still early stage and needs a fair amount of improvements, but gives some more hints about whats going on.
Logs are written in the same directory you run the tool in.
...and support for quite some new devices!
@SigmundDroid : Now the support for the Fairphoen 3 should be fixed and TWRP should work A/B devices (tested with google pixel 3a). Give it a try, if you want!
I would be grateful about any feedback! Let me know how it works for you!

Just tried the 2nd version:
+ Nice, comes with log now, good!
- failed at fastboot_oem_unlock twice... but actually it was the "fastboot flashing unlock" (not the oem). Not sure about the proper names for these two unlock (one in dev settings and the other one per fastboot). So, I set both correctly and restarted but it kept hanging here (and no way to skip your test).
The TWRP install worked well... just, how do I start it later? It was installed on A and on B is the LOS recovery - is there some easy way to use TWRP? (really don't have a clue as A/B is fairly new to me)
PS: Shall I drop you the log somewhere?

SigmundDroid said:
Just tried the 2nd version:
Click to expand...
Click to collapse
Great! Thanks a lot!
SigmundDroid said:
+ Nice, comes with log now, good!
Click to expand...
Click to collapse
Thanks! Did you also try the "advanced output" feature?
SigmundDroid said:
- failed at fastboot_oem_unlock twice... but actually it was the "fastboot flashing unlock" (not the oem). Not sure about the proper names for these two unlock (one in dev settings and the other one per fastboot). So, I set both correctly and restarted but it kept hanging here (and no way to skip your test).
Click to expand...
Click to collapse
That's a very good catch, I noticed an issue there. I followed this official tutorial from Fairphone: https://support.fairphone.com/hc/en-us/articles/360048646311-Manage-the-bootloader-of-your-FP3-FP3-
And they used `fastboot oem unlock`, which I noticed now doesn't even exist. I fixed it now.
SigmundDroid said:
The TWRP install worked well... just, how do I start it later? It was installed on A and on B is the LOS recovery - is there some easy way to use TWRP? (really don't have a clue as A/B is fairly new to me)
Click to expand...
Click to collapse
Ah, right now, I just boot to TWRP recovery, not flash it for A/B devices, since I was not sure how to best do it for now (without potentially destroying stuff). For Samsung devices it will be flashed.
Do you think this is an issue in general? I might try to add it as a feature for power users, that can also handle the risk a bit better. What do you think?
SigmundDroid said:
PS: Shall I drop you the log somewhere?
Click to expand...
Click to collapse
For now, it's fine and I guess I know whats the issue.
I'm planning another release next week, probably mostly a bugfixing and user-interface release. I will post it here again

Hey there!
Today I released the Version v.0.3.0-alpha of the OpenAndroidInstaller with many improvements and newly supported devices!
The release includes 11 new devices (now 27 officially supported devices):
Motorola moto g7 power (ocean)
Motorola moto g5 (cedric)
Samsung Galaxy Note 9 (crownlte)
Samsung Galaxy Note 10 (d1)
oneplus 6
oneplus 6T
oneplus 7
oneplus 7 Pro
oneplus 7T
oneplus 7T Pro
OnePlus Nord N200
Give it a try, if you want!
I would be grateful about any feedback! Let me know how it works for you!

Clean shot, eh!
No, really, worked like a charm! No hickups, nothing, just awesome! Thanks!
PS: Fun fact... Yes, one hickup: Was trying to use LOS recovery three times in a row until I realized it should be TWRP

SigmundDroid said:
Clean shot, eh!
No, really, worked like a charm! No hickups, nothing, just awesome! Thanks!
PS: Fun fact... Yes, one hickup: Was trying to use LOS recovery three times in a row until I realized it should be TWRP
Click to expand...
Click to collapse
Great! Thanks a lot for testing again!
Looks like the thing is slowly moving to a more stable state. Maybe moving to beta next year
PS: Good point! In the next release I will try to make it clearer. At least you could not use the LOS recovery

__sterby__ said:
will try to make it clearer. At least you could not use the LOS recovery
Click to expand...
Click to collapse
Yeah, perhaps some bold print of the file templates for unteachable people like me Nah, just kidding...
In any case, thanks so far and Merry XMAS

SigmundDroid said:
Yeah, perhaps some bold print of the file templates for unteachable people like me Nah, just kidding...
In any case, thanks so far and Merry XMAS
Click to expand...
Click to collapse
Thanks a lot! Merry Christmas to you as well!

Hey everyone!
I did some work in the last weeks and now the OpenAndroidInstaller is available in alpha version 0.3.1, with improved user experience and newly supported devices.
New features:
new images to guide in the process
steps indicator header
remove step-progressbar and move the header to different column container to keep it attached to the top
pop-up box to explain custom recovery and OS images.
dialog to help finding the android or firmware version
5 New devices (now 32 officially supported devices):
Sony Xperia 10 (kirin)
Sony Xperia 10 Plus (mermaid)
Sony Xperia XA2 (pioneer)
Sony Xperia XZ3 (akatsuki)
Sony Xperia XZ2 (akari)
If you're interested in trying out alternative ROMs on your device, now is the perfect time to give OpenAndroidInstaller a try. Over the holiday season, you might to play with OpenAndroidInstaller on your old or new devices and see what it can do.
Thank you for supporting open source software and giving OpenAndroidInstaller a chance. Happy holidays and happy installing!
PS: There is a brand new, shareable website now! https://openandroidinstaller.org/

Hey you all! I have been quiet for while here, but the work continued!
Now I'm happy to release the first beta release of the OpenAndroidInstaller.
The major new feature is the option to install addons like GApps, MicroG or F-droid with the Installer. Also there are now 52 officially supported devices and more to come!
If you want to try it, I'm happy about all kind of feedback (positive and negative). Have a great day and happy flashing!
Release: https://github.com/openandroidinstaller-dev/openandroidinstaller/releases/tag/v0.4.0-beta
Download: https://openandroidinstaller.org/download.html