Hi ! Gentlemen
I found this rom by chance on one of my favorite websites. I wanted to share that with you.
Hello everyone!
For those who think that their smartphone is already a computer, our small team proposes to use your smartphone as the central unit of any screen: monitor, TV or video projector
Like MS Windows Continuum but better
We are developing a new window manager for Android for a new user experience. You can now use multitasking / multi-windows, resizing, folders and shortcuts on the desktop. You will find a "start" menu, application dock, notifications management, etc.
You can display this interface directly on the screen of your phone / tablet but the most interesting is to use it on a second screen connected with or wireless (respectively MHL / DisplayPort / DisplayLink or Miracast or even Chromecast).
The cherry on the cake, you keep the use of your smartphone since we dissociate the displays of the 2 screens and their uses.
Our code is based on CyanogenMod 13.0. We will shortly pass our development branches on LineageOS 14.1. The goal is to maximize compatibility based on this distribution.
After installation you will find 4 pre-installed applications:
OXI: Launches OXI on the main screen of the device
OXI Remote: Launches OXI on the secondary screen (Android must already be connected to another screen in "mirror" mode, in MHL, DisplayPort, Miracast ...)
We strongly recommend using a Microsoft Wireless Display v2 (available on Amazon, FNAC, etc.) or ActionTech branded adapter, which is fully compatible with OXI and eliminates mouse latency. Feel free to try with your material and give us your feedback.
OXI Control: A small utility if you do not have a Bluetooth keyboard or mouse. Two modes are possible, "Keypad" mode is a simple touchpad and keyboard on the phone, "pad" mode allows to play games requiring tactile use
In some cases, mainly on televisions, the image may not be fully displayed and trimmed. Adjust using this utility until you see the red rectangle around the blue
Youtube video :
https://www.youtube.com/watch?list=PLAnO2gXcwt07ZVIfV_kgfdMUtgxGFSDr6&v=eLM_7da1W0E
View Original French Source Frandroid :
http://forum.frandroid.com/topic/254306-alpha-oxi-sur-nexus-5x/
Installation
If your smartphone is already on CyanogenMod13, you will be able to install the OXI ROM without having to reset your smartphone, just install the zip file "on top". If you have a problem with Google Apps, reinstall them via Open GApps immediately after installing OXI.
OXI installs itself as CyanogenMod 13. If you have another favorite tutorial, do not hesitate to follow it, the procedure being similar to all phones.
If you have not already done so, you need a phone with TWRP or another custom recovery to install zip files. To do this, you will have to unlock the bootloader (with consequences on what it implies), flasher via fastboot or another proprietary tool (Odin, spflashtool ...) to set up the recovery custom partition.
Once in recovery, enjoy to backup your system partitions (including EFS).
Perform a complete wipe the phone (you can try if you are on a CM13 compatible rom to not perform wipe)
Install OXI via adb sideload or by dropping and selecting the .zip file.
If necessary, install the Google apps in the same way (download the corresponding .zip from http://opengapps.org/, select Android 6.0.
Restart the phone and you should be ready to test OXI
For more details I invite you to follow for example this tutorialImportant! Instead of applying root, apply OXI and then Google Apps via OpenGApps
Http://forum.frandroid.com/topic/234137-tuto-installation-recovery-custom-et-root-nexus-5x/
DownloadOXI 0.1.4 (26/01/2017) - md5 0304ee4f69fc6894ae1c42b3501ab670Need Vendor MTC20K 6.0 MM
Via mega.nz: https://mega.nz/#!jt91FI4K!oLeUd3mGWvErpz-96cPl0wqEjK5xPHyP_9laMxf-S0M
Via androidfilehost: https://www.androidfilehost.com/?fid=529152257862698698
Warning:
You install this ROM of your own volition and we are not responsible for any direct or indirect damage to your phone, your data or any consequence related to the OXI test. Back up your data before installing as well as the partitions (Golden Rule).
Oxi is in alpha version, stable enough but still small bugs / crash OXI (not Android) and possibly flaws - do not use in production environment.
We are still developing and we will certainly offer here updates according to the returns obtained
The downgrade since CyanogenMod / LineageOS 14.0 / 14.1 is likely to fail without wipe data / system
Below is a list of the current limitations of OXI. We strive to remove these limitations as we develop.
If you find others, it will feed our todo!
Chromecast is supported but will not work with mouse latency optimizations. Same comment on some Miracast implementations in TV.
If you have problems installing new applications or launching them (for permissions), try launching the application first on the phone in the usual way.
There may be minor problems not related to OXI, these are probably related to CyanogenMod 13
Shortcuts on the desktop are only saved when you exit the application
The bluetooth management from OXI does not work (yet)
Some applications (especially some games) do not resize correctly. Some Unity games can even crash when resized, we work on it.
The optimal configuration is full HD (1920x1080) on an external monitor (PC monitor or TV)
Some TVs unfortunately do not indicate their actual size, in this case the applications will potentially be displayed "bigger" than necessary (similar problem with DisplayLink). We are also working on that.
A single instance of an application can be launched in OXI
An application can only be launched in OXI or on the phone but never both.
The ROM does NOT include any Google apps, but you can install them manually (in the same way as CyanogenMod after installing the .zip - do not do it again if you update from CyanogenMod 13)
The overscan tool may need to be forcibly closed (via reboot, recent apps or any other means) if the setting display persists.
SourcesOur code is based on CyanogenMod 13 (Apache 2): https://github.com/CyanogenMod and http://cyanogenmod.org (down ...)
Nexus 5X kernel sources (GPL): https://github.com/cyanogenmod/android_kernel_lge_bullhead
Websites : https://www.auxens.com/
View Original French Source Frandroid :
http://forum.frandroid.com/topic/254306-alpha-oxi-sur-nexus-5x/
I have try this Rom and it's a simple Cyanogenmod 13 6.0 Marshmallow with Oxi system you can switch to cyanogenmod into Oxi Os and invert. I have try with simple chromecast and it's work like a charm
Tell me what you think of this rom in the comments in advance thank you and beg you to believe in my sincere greetings
Screenshot :
[url=http://www.hostingpics.net/viewer.php?id=592168Screenshot20170204173617.png]
[/URL]
[url=http://www.hostingpics.net/viewer.php?id=795672IMG20170204183846.jpg]
[/URL]
{
"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"
}
For Moderators :
I don't know if I have the right or not to share this work that is not mine. I apologize in advance if I have done wrong
sorry
Seems nice, but instead of repeating and saying basic things like "You need to install TWRP first" or "Don't forget to backup" you could introduce the project to us.
I don't know French, thus I have absolutely no idea what is this about. Few of my questions:
1. What is that? Given you wrote "Turn your Nexus 5x in computer", I suppose it's smth like Continuum. But there's not enough details.
2. How does it work? AFAIK Nexus 5X's USB Type-C port doesn't support HDMI out.
3. Which vendor to use with it?
4. Which build of CM13?
5. Is it standalone/different OS, or just skin/modification for CM13 to work better on larger screens?
6. Is there difference between this and app Taskbar combined with Nougat (Freeform mode)?
neth15 said:
Seems nice, but instead of repeating and saying basic things like "You need to install TWRP first" or "Don't forget to backup" you could introduce the project to us.
I don't know French, thus I have absolutely no idea what is this about. Few of my questions:
1. What is that? Given you wrote "Turn your Nexus 5x in computer", I suppose it's smth like Continuum. But there's not enough details.
2. How does it work? AFAIK Nexus 5X's USB Type-C port doesn't support HDMI out.
3. Which vendor to use with it?
4. Which build of CM13?
5. Is it standalone/different OS, or just skin/modification for CM13 to work better on larger screens?
6. Is there difference between this and app Taskbar combined with Nougat (Freeform mode)?
Click to expand...
Click to collapse
Like MS Windows Continuum but better
It work with miracast or chromecast for share the screen
it's based on Cyanogenmod 13 but modified
i haven't test this rom but for the vendor i think it's the latest 6.0 Marshmallow
you can go to see the github and website for more info
OP Refresh for more info
Renaf2 said:
OP Refresh for more info
Click to expand...
Click to collapse
Much, much better Thanks bro
Don't get me wrong, I just wanted you to put all the functions, screens etc. together. It's easy to just link to the other website, but less effective than describing it
Btw. I guess I'll try it, but first I'll buy the adapter.
neth15 said:
Much, much better Thanks bro
Don't get me wrong, I just wanted you to put all the functions, screens etc. together. It's easy to just link to the other website, but less effective than describing it
Btw. I guess I'll try it, but first I'll buy the adapter.
Click to expand...
Click to collapse
If you have a chromecast you can try
Renaf2 said:
If you have a chromecast you can try
Click to expand...
Click to collapse
I don't have one. But this app seems pretty good (I have spare computer). Did you try it?
neth15 said:
I don't have one. But this app seems pretty good (I have spare computer). Did you try it?
Click to expand...
Click to collapse
No try it at this moment sorry and i have the honor 6x now
I try it in few minutes
The Vendor.img is MTC20K
it's a simple Cyanogenmod Rom with Oxi system into it
Excellent
[url=http://www.hostingpics.net/viewer.php?id=592168Screenshot20170204173617.png]
[/URL]
i have try that with my chromecast and work like a charm no problem here just cast your screen in quick settings in notification and run oxi remote if you haven't mouse and keyboard you can use oxi control for that you have the keypad for mouse and keyboard and if you want to play you have the pad for that
[url=http://www.hostingpics.net/viewer.php?id=795672IMG20170204183846.jpg]
[/URL]
Hi everyone! Lead dev here!
I'm really surprised and happy to see that our work traveled to XDA without me posting it Thank you renaf2, no problem to share it here.
I'm not able to write a long message tonight (Murphy's Law, I'm in the country side with low network and no physical keyboard) but don't worry I'm gonna be more present here next week.
First of all I know there is a quite huge bug (and my fault sorry!) with Google Apps in this version. I'm gonna publish a new version around Monday or Tuesday.
Beth15, to answer shortly:
1. (This is the long to answer question! I guess Renaf2 clarifications are really helpful but we have so much more to tell!)
2. With nexus 5x we tried DisplayLink (wired), Chromecast (working but not optimal for latency), Miracast (with Microsoft adapters) and what I call "local mode" (directly on the smartphone screen).
3/4. That's a good question... My focus is more on OXI itself than the system so I can't tell from memory which build is used (I would say MOB31K for the build and last rebase from cm repositories was from early December)
Btw thanks Renaf2 for the clarification on the vendor versions. I will be more precise (including in the French topics) next time, I promise
5. It's a modified Android system working with the OXI app. We don't want to disrupt the "classic" Android behavior and we are really in a "adding something missing" than "transforming it" state of mind. Not just screen display tweaking also.
6. It's different for multiple reasons: remote display, session conservation, no requirement for apps developers, enhanced latency in wireless, better window management... And we're working on a lot of other features
I will write more soon!
If you have any question feel free to ask, I'll be glad to answer!
0x4A4A said:
Hi everyone! Lead dev here!
I'm really surprised and happy to see that our work traveled to XDA without me posting it Thank you renaf2, no problem to share it here.
I'm not able to write a long message tonight (Murphy's Law, I'm in the country side with low network and no physical keyboard) but don't worry I'm gonna be more present here next week.
First of all I know there is a quite huge bug (and my fault sorry!) with Google Apps in this version. I'm gonna publish a new version around Monday or Tuesday.
Beth15, to answer shortly:
1. (This is the long to answer question! I guess Renaf2 clarifications are really helpful but we have so much more to tell!)
2. With nexus 5x we tried DisplayLink (wired), Chromecast (working but not optimal for latency), Miracast (with Microsoft adapters) and what I call "local mode" (directly on the smartphone screen).
3/4. That's a good question... My focus is more on OXI itself than the system so I can't tell from memory which build is used (I would say MOB31K for the build and last rebase from cm repositories was from early December)
Btw thanks Renaf2 for the clarification on the vendor versions. I will be more precise (including in the French topics) next time, I promise
5. It's a modified Android system working with the OXI app. We don't want to disrupt the "classic" Android behavior and we are really in a "adding something missing" than "transforming it" state of mind. Not just screen display tweaking also.
6. It's different for multiple reasons: remote display, session conservation, no requirement for apps developers, enhanced latency in wireless, better window management... And we're working on a lot of other features
I will write more soon!
If you have any question feel free to ask, I'll be glad to answer!
Click to expand...
Click to collapse
You can open a new theard in apropriate section and i ask to delete this theard if you want no problem i just want to share your interesting and great work
I'm happy to meet you
Sinon je suis aussi sur frandroid meme pseudo mais je n'y vais plus je suis a la source maintenant sur xda c'est mieux pour apprendre
Hi everyone !
Sorry, I was really busy those days to be able to post around here (and right now I can't post in the proper forums sections), and trying to port it to Nougat (not so easy )
You can find an update for Nexus 5X on the main topic, with a bit more info : https://forum.xda-developers.com/android/general/rom-oxi-smartphone-computer-oneplus3-t3558293
0x4A4A said:
Hi everyone !
Sorry, I was really busy those days to be able to post around here (and right now I can't post in the proper forums sections), and trying to port it to Nougat (not so easy )
You can find an update for Nexus 5X on the main topic, with a bit more info : https://forum.xda-developers.com/android/general/rom-oxi-smartphone-computer-oneplus3-t3558293
Click to expand...
Click to collapse
Oh yeah thank you so much for your hard work bro
Renaf2 said:
Hi ! Gentlemen
I found this rom by chance on one of my favorite websites. I wanted to share that with you.
Hello everyone!
For those who think that their smartphone is already a computer, our small team proposes to use your smartphone as the central unit of any screen: monitor, TV or video projector
Like MS Windows Continuum but better
We are developing a new window manager for Android for a new user experience. You can now use multitasking / multi-windows, resizing, folders and shortcuts on the desktop. You will find a "start" menu, application dock, notifications management, etc.
You can display this interface directly on the screen of your phone / tablet but the most interesting is to use it on a second screen connected with or wireless (respectively MHL / DisplayPort / DisplayLink or Miracast or even Chromecast).
The cherry on the cake, you keep the use of your smartphone since we dissociate the displays of the 2 screens and their uses.
Our code is based on CyanogenMod 13.0. We will shortly pass our development branches on LineageOS 14.1. The goal is to maximize compatibility based on this distribution.
After installation you will find 4 pre-installed applications:
OXI: Launches OXI on the main screen of the device
OXI Remote: Launches OXI on the secondary screen (Android must already be connected to another screen in "mirror" mode, in MHL, DisplayPort, Miracast ...)
We strongly recommend using a Microsoft Wireless Display v2 (available on Amazon, FNAC, etc.) or ActionTech branded adapter, which is fully compatible with OXI and eliminates mouse latency. Feel free to try with your material and give us your feedback.
OXI Control: A small utility if you do not have a Bluetooth keyboard or mouse. Two modes are possible, "Keypad" mode is a simple touchpad and keyboard on the phone, "pad" mode allows to play games requiring tactile use
In some cases, mainly on televisions, the image may not be fully displayed and trimmed. Adjust using this utility until you see the red rectangle around the blue
Youtube video :
https://www.youtube.com/watch?list=PLAnO2gXcwt07ZVIfV_kgfdMUtgxGFSDr6&v=eLM_7da1W0E
View Original French Source Frandroid :
http://forum.frandroid.com/topic/254306-alpha-oxi-sur-nexus-5x/
Installation
If your smartphone is already on CyanogenMod13, you will be able to install the OXI ROM without having to reset your smartphone, just install the zip file "on top". If you have a problem with Google Apps, reinstall them via Open GApps immediately after installing OXI.
OXI installs itself as CyanogenMod 13. If you have another favorite tutorial, do not hesitate to follow it, the procedure being similar to all phones.
If you have not already done so, you need a phone with TWRP or another custom recovery to install zip files. To do this, you will have to unlock the bootloader (with consequences on what it implies), flasher via fastboot or another proprietary tool (Odin, spflashtool ...) to set up the recovery custom partition.
Once in recovery, enjoy to backup your system partitions (including EFS).
Perform a complete wipe the phone (you can try if you are on a CM13 compatible rom to not perform wipe)
Install OXI via adb sideload or by dropping and selecting the .zip file.
If necessary, install the Google apps in the same way (download the corresponding .zip from http://opengapps.org/, select Android 6.0.
Restart the phone and you should be ready to test OXI
For more details I invite you to follow for example this tutorialImportant! Instead of applying root, apply OXI and then Google Apps via OpenGApps
Http://forum.frandroid.com/topic/234137-tuto-installation-recovery-custom-et-root-nexus-5x/
DownloadOXI 0.1.4 (26/01/2017) - md5 0304ee4f69fc6894ae1c42b3501ab670Need Vendor MTC20K 6.0 MM
Via mega.nz: https://mega.nz/#!jt91FI4K!oLeUd3mGWvErpz-96cPl0wqEjK5xPHyP_9laMxf-S0M
Via androidfilehost: https://www.androidfilehost.com/?fid=529152257862698698
Warning:
You install this ROM of your own volition and we are not responsible for any direct or indirect damage to your phone, your data or any consequence related to the OXI test. Back up your data before installing as well as the partitions (Golden Rule).
Oxi is in alpha version, stable enough but still small bugs / crash OXI (not Android) and possibly flaws - do not use in production environment.
We are still developing and we will certainly offer here updates according to the returns obtained
The downgrade since CyanogenMod / LineageOS 14.0 / 14.1 is likely to fail without wipe data / system
Below is a list of the current limitations of OXI. We strive to remove these limitations as we develop.
If you find others, it will feed our todo!
Chromecast is supported but will not work with mouse latency optimizations. Same comment on some Miracast implementations in TV.
If you have problems installing new applications or launching them (for permissions), try launching the application first on the phone in the usual way.
There may be minor problems not related to OXI, these are probably related to CyanogenMod 13
Shortcuts on the desktop are only saved when you exit the application
The bluetooth management from OXI does not work (yet)
Some applications (especially some games) do not resize correctly. Some Unity games can even crash when resized, we work on it.
The optimal configuration is full HD (1920x1080) on an external monitor (PC monitor or TV)
Some TVs unfortunately do not indicate their actual size, in this case the applications will potentially be displayed "bigger" than necessary (similar problem with DisplayLink). We are also working on that.
A single instance of an application can be launched in OXI
An application can only be launched in OXI or on the phone but never both.
The ROM does NOT include any Google apps, but you can install them manually (in the same way as CyanogenMod after installing the .zip - do not do it again if you update from CyanogenMod 13)
The overscan tool may need to be forcibly closed (via reboot, recent apps or any other means) if the setting display persists.
SourcesOur code is based on CyanogenMod 13 (Apache 2): https://github.com/CyanogenMod and http://cyanogenmod.org (down ...)
Nexus 5X kernel sources (GPL): https://github.com/cyanogenmod/android_kernel_lge_bullhead
Websites : https://www.auxens.com/
View Original French Source Frandroid :
http://forum.frandroid.com/topic/254306-alpha-oxi-sur-nexus-5x/
I have try this Rom and it's a simple Cyanogenmod 13 6.0 Marshmallow with Oxi system you can switch to cyanogenmod into Oxi Os and invert. I have try with simple chromecast and it's work like a charm
Tell me what you think of this rom in the comments in advance thank you and beg you to believe in my sincere greetings
Screenshot :
[url=http://www.hostingpics.net/viewer.php?id=592168Screenshot20170204173617.png]
[/URL]
[url=http://www.hostingpics.net/viewer.php?id=795672IMG20170204183846.jpg]
[/URL]
For Moderators :
I don't know if I have the right or not to share this work that is not mine. I apologize in advance if I have done wrong
sorry
Click to expand...
Click to collapse
Love the idea but the UI looks awful, i don't dig it, not one bit... I like the idea that you want to bring this to other devices, because so far the only ones that have this feature are all lumias, samsung s8 and the new huawei. I offer to help with the UI, to make it prettier.
Related
***ATTENTION IF YOU ARE COMING FROM A 4349+ STOCK ROM or MOD based off that PLEASE VISIT THE FOLLOWING LINK TO DOWNGRADE YOUR BOOTLOADER AND TNT VERSION BEFORE FLASHING CWM AND THIS OR ANY OTHER ROM****
http://forum.xda-developers.com/showthread.php?t=1036956
LINK TO NEWEST DEVELOPMENT: VEGAn-TAB GINGEREDITION: http://forum.xda-developers.com/showthread.php?t=1031250
VEGAn 1.00 beta 5.1.1 supplement - Thanks Roebeet for staying on top of it!
Link: http://www.mediafire.com/?jhq1cnu5wgkg3j5
md5sum: 7f3920a3ef2dabf264bfc8550d8f6d00
List of fixes / enhancements in this supplement:
- Maps 5.1 with the rotation fix
- Market 2.2.11
- Updated drivers that should bump up Quadrant slightly, and significantly improves Nenamark scores
- Frame rate change from 50 to 60
- Replaced the Froyo keyboard with the Gingerbread keyboard
- Added Adam Sniffer app, and their keyboard as an option
Quick instructions: This is a supplement, not a full firmware. You would run this like any other update.zip, but since the changes are small you shouldn't have to wipe data. You'd want beta 5.1 as your baseline, before running this, download link is further below for the full install of beta 5.1.
I know that the VEGAn users probably haven't been "feeling the love" the last few weeks, so we wanted to at least bump you up to some of the latest changes ported to TNTL. I have been plugging away hard on CM7 and VEGAn-TAB GingerEdition and rothnic's expertise with a lot of the these enhancements are the reason why they exist right now. The Nenamark bump actually originated from our Adam testing, believe it or not.
As Per usual USE THIS ROM AT YOUR OWN RISK. We highly recommend clockworkmod recovery as a pre-req. We are only testing for cwm users.
I would also recommend a full data wipe between updates, at least for now when we reach STABLE RELEASE stage this may not be always necessary. There is a great tool out there you can use if you don't know about it already called Titanium Backup it is on the market and there is a free version. It allows you to backup/restore all your apps and even save/restore data for those apps... the only caveat I will say is do not restore any system apps (ie. apps preloaded with our roms) this can cause issues.
****The First Boot after installing BETA 5.1 will take a few minutes to catch up and will feel "laggy" this depends on how much media you have on your device for it to scan in the first time****
**If you are having issues with the new market telling you you don't have enough space to download then your SD Partitions are incorrect and need fixed** -Boot Clockworkmod, select advanded, then partition SD, 2048 for first option, and 0 for second. process will take ~10 mins ******WARNING THIS WILL DELETE EVERYTING ON SDCARD (internal) MAKE A BACKUP!!!!******
Now that we are nearing a STABLE Release here are some new links you may not be aware of:
Build URL: http://vegantab.gojimi.com/
Downloads section: http://vegantab.gojimi.com/downloads
ON TO THE ROM:
***UPDATE***
1.0.0 Beta5.1 Link: http://vegantab.gojimi.com/download/gtab.VEGAn.1.00.beta5.1.user.final.zip
md5sum: a01171d77f25444088ecc884c793d105
This is an update.zip formatted file. You'd run this like you'd run any other update.zip file.
-----------------------------------------------
ONLY DO THIS IF YOU DO NOT CARE ABOUT G-SENSOR BEING RIGHT FOR MOST G-SENSOR GAMES & WOULD RATHER HAVE MOUSE SUPPORT BACK -- *****PATCH TO REMOVE G-SENSOR FIX AND RESTORE MOUSE SUPPORT***** - ONLY INSTALL THIS AFTER BETA 5: http://vegantab.gojimi.com/download/patch.VEGAn.BETA5.remove.Gsensor.zip **Flash this like you do the roms in clockwork**
This is a collaboration between myself, Roebeet, and Rothnic - The G-TabDevs Team.
BETA 5 changes:
* NEW KERNEL **Thank you Rothnic** We have compiled alot of new features in to this with more on it’s way at some point.
* LAG on WAKE FIX! woo hoo! no more laggy tablet after sleeping.
* CIFS support (allows mounting shared folders over a network) – search CIFS in the android market for apps
* NTFS support (this gives us the ability to mount drives formatted NTFS which is popular on Windows machines…. Larger File Support)
* Ethernet on DOCK Support (This will only work right now if the device is booted while connected to the dock to activate the port)
* ***UPDATED EVEN BETTER****G-Sensor Fix (this has been long awaited by many! Fixes most games that use the g-sensor for controls, etc.) **this is a DIRTY FIX but it works… only issue is it does mess up mouse usage… so if you are a mouse user and don’t care about the g-sensor being right for games there is a patch below that you can apply ***AFTER*** you install BETA 5.
* REBOOT OPTION has now been added to the power menu. Remember that popup menu is a scrollable menu so if you don’t see it all use your finger and scroll on down!
* I increased the DELAY for the LONGPRESS Power button to bring up the menu… it is now a full second. This has dramatically decreased the number of time the power menu has accidentally popped up when trying to wake the device.
* Added the Tablet Compatible Stock Calendar that I dropped on you guys at Christmas on the Website.
No Major theme changes, nor some of the other fixes that I have been having issues with. The next release should include those. This is the LAST BETA I believe. The next release will take some time so settle in for a bit while we work on Release Candidate 1.
-------------------------------------------------------------------
Benefits to us
- Soft buttons, like TnT. But no TnT UI layer getting in our way. So, for example, keyboard replacements should work.
- Just as fast as the new builds we have if not FASTER.
- Vega build has a bootup script where we can install user-based apks, after a data wipe. So, for example, Flash is now added to the build.
- Vega firmware development is probably more active than the official TnT development, at least from the little I've seen so far (though TnT have been fairly active lately).
Known issues
- Videos are not being automatically scanned on the EXTERNAL SDCARD.
*****FIXED**** Weird orange bar is showing up in the stock Calendar app *****FIXED****
- The newest Market apk seems to have issues with any device that's been re-partitioned outside of the default of 2048. The "fix" is to re-partition your SD back to the default of 2048, in clockworkmod. Thanks to proengin for informing us of this.
Changelog
- (a2) We are using alpha1 as our "base" image, and then a modular format on top of that. So, alpha2 is a full update.zip package.
- (a2) VOLD should be fixed using a hack. 30 seconds after bootup, SDCARD2 should start working. Or, it may not work. It's an alpha.
- (a2) Vega user apk script has been added, which is supposed to add Flash on a newly wiped system. But it's spotty at best.
- (a2) Camera should be fixed.
- (a2) We're deleting some of the unneeded system apps like Twitter, Facebook, the Htc stuff in gapps and talkback. You can always add these back via the Market. The reason is to keep the image a little cleaner.
- (a2) Audio fix added.
- (a3) Added changes to the framework for smaller status bar and VEGAn boot screen.
- (a3) Added Gingerbread keyboard.
- (b1) SSL bug fixed. Also, added the latest YouTube and Gmail apps. Removed the user apk script for now, as it's really buggy.
- (b2) VOLD post-boot replaced with a mount commend. Should be more stable and might fix the disappearing apps, I hope. New Gmail, adhoc wireless support added, adfree hosts file removed (get "adfree android" app in the market to get it back), removed the Phone apks which should improve battery life.
- (b3) Mounting issues should be completely corrected, audio issues are corrected, new rothnic theme added, new Gmail and Voice apps, new Settings app with advanced Wifi (and policy is set to "never sleep" by default).
- (b4) A New Cleaner Base System Image with the addition of files from new Advent Vega Release (we can finally get rid of the hacked together Image That I originally created for VEGAn)
- (b4) New Kernel (from latest unreleased TNT Update kernel version #15)
- (b4) New Boot Logo(replaces G-Tablet on white background)
- (b4) New VOLD Binary and MediaProvider(allows media to be seen from External SD Card as well as internal)(videos are not being automatically found on SDCARD2 ATM I am working on that)
- (b4) Settings app no longer has Call Settings option or mobile networks as it is not a phone
- (b4) New Market (We have got it showing even more apps... but still not all. Still need to do the market hack.)
- (b4) Some Graphics and Performance Improvements reduces video tearing issue among other improvements (G-TabDevs Performance Pack)
- (b4) New Music Player(pulled the one from CM6.1 and got it running on VEGAn)
- (b4) framework laid for bluetooth HID(not sure if it is fully functional yet please let us know if it work for you)
- (b4) laid the framework for POSSIBLE OPENVPN support(not fully functional yet sure if I can get it to work yet)
- (b4) New Theme Improvements - Switched to a more Cyan color highlights (the previous green may be available as a small update at a later date.
- (b4) Flash now auto installs on first boot up usually after about 15 secs so the tablet can finish booting
1.0.0 Beta 5:
{
"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"
}
------------------------------------------------------------------
Archives:
1.0.0 Beta3 Link: http://www.mediafire.com/?tt3n3njojetnscx
Alternate link: http://www.megaupload.com/?d=3KJ799TZ
md5sum: fea915609ab56aa233fabcfff3bcc2a3
1.0.0 Beta2 Link: http://www.mediafire.com/?c9a1c11zz1wgza9
Alternate link: http://www.megaupload.com/?d=MKKNTZP1
md5sum: 1b16d0cf7f02702a6796914195d8339b
1.0.0 Beta1 Link: http://www.mediafire.com/?5hr09gj53ut1208
Alternate link: http://www.megaupload.com/?d=Y9NR34AD
md5sum: 2906ed4fd5ae4fc1954b7b5e766f1507
1.0.0 Alpha3 Link: http://www.mediafire.com/?tzhc7vtstdl128x
Alternate link: http://www.megaupload.com/?d=9SPCOMPY
md5sum: 148a7bf52458cbedc9d859e91281a6c8
1.0.0 Alpha2 Link: http://www.mediafire.com/?bdurosaclrp4r3i
Alternate link: http://www.megaupload.com/?d=H264QQRH
md5sum: 2541fccfb01fb8b398fc38beaa5b3355
1.0.0 Alpha1 : http://forum.xda-developers.com/show...5&postcount=57
Stuck thread
I hope you have a lot of bandwidth on that server, gojimi, because you're about to get hammered. Might want to consider uploading through multiupload.com, the service roebeet's been using.
Downloading and getting ready to flash here, btw.
Downloading now! thanks for all the fast updates!!
Thanks for the hard work!!!!!! Downloading now
Ahh! didnot bring Gtab to work !
Will D/L after work.
Thank you Santa Clause ('s)
LOL.
And I just got done loading up the new latest VS ROM. It's much better, but it still ain't Vegan.
Oh well, I got no problem swapping out ROMS. Thanks for the hard work guys.
Thank You!!Just updated then did the TnT Kb + Live WP + Gapps..Formatted SD 2048 / 0 ..Did Market Fix and Im In....
Love the new Image instead of the gtab image.....
Can't decide on the bios or this boot logo..
Quadrant 2463
Thanks Again!!
looking sexy downloading now!!!
Is there any way to have the Home button bring up the launcher instead of the Clock app? Or am I experiencing a unique issue?
HID Testing
How do I enable the bluetooth HID? I am trying to connect to my keyboard, but I don't see any option for it?
It does bring up the generic message to try "0000" or "1234" however it did not work, or do I mis understand? is this something I need to do at the command line hidd --connect etc?
Everything else seems to work great, at least what I have tested.
Thanks !
Wiped everything before install. Runs well, but noticed a few issues.
First, my power button stopped putting the device to sleep. I could hold and get the shutdown menu. Reboot fixed this.
Second, if you use the lock screen feature and try to log in before the device finishes starting up (after a power on or reboot) the touchscreen becomes unresponsive. You have to hold down the power button for 10 seconds to force shutdown. Noticed this with beta 3 as well.
Third, hacked TSCalibration doesn't appear to be proloaded to find INI file on root of /sdcard instead of /sdcard2.
Seems great other than that!
So far so good! Wiped data, cache, and dalvik then installed. Got TB and restored my Pro license, then selected apps with data (no system data) to restore. Entered in Gmail account, tested Market. Applied Swype install/hack and rebooted. Running smooth, Quadrant in the 2400+ range.
The only problem I have is I can't sync my Facebook account under Accounts. I don't need this per se, but I'd like to have them.
-=Sent from my Droid 2 (Fission 2.4.3) using Tapatalk=-
schauerd said:
How do I enable the bluetooth HID? I am trying to connect to my keyboard, but I don't see any option for it?
It does bring up the generic message to try "0000" or "1234" however it did not work, or do I mis understand? is this something I need to do at the command line hidd --connect etc?
Everything else seems to work great, at least what I have tested.
Thanks !
Click to expand...
Click to collapse
I wasn't totally sure I had bluetooth HID licked this round or not... I don't have a bluetooth keyboard to test with... looks like we are part way there maybe by the next build we'll have a better understanding of what needs done.
ehunyadi said:
Is there any way to have the Home button bring up the launcher instead of the Clock app? Or am I experiencing a unique issue?
Click to expand...
Click to collapse
Ehunyadi: you are one of only two people experiencing this issue. I would like to know what the model number of your tablet is. On the back starts with UPC3*** etc. It seems this may be linked to a specific run of devices but we are not sure. Let me know so I can track down the root cause of this.
gojimi said:
Ehunyadi: you are one of only two people experiencing this issue. I would like to know what the model number of your tablet is. On the back starts with UPC3*** etc. It seems this may be linked to a specific run of devices but we are not sure. Let me know so I can track down the root cause of this.
Click to expand...
Click to collapse
Model: UPC300-2.2
ehunyadi said:
Model: UPC300-2.2
Click to expand...
Click to collapse
I have the same model number and my home buttons work fine.
Thanks for the response !
ehunyadi said:
Model: UPC300-2.2
Click to expand...
Click to collapse
Now that's weird... I guess it is not model specific then... It seems like something is telling it the tablet is docked when it clearly is not. Just to clarify did you do a full data/cache wipe in Clockwork Mod after installing BETA 4?
Just trying to run through the troubleshoot list.
Was loudness increased? Seems louder. Also seems a tad quicker.
{
"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"
}
We now have a Q&A thread HERE please use this for questions about the project. This thread is for development only!
This project started off in this forum here: http://forum.xda-developers.com/showthread.php?t=1390351
However since then the project has grown and just keeps growning! Featuring a ever growing range of distros
The TEAM!
The team consist of:
zacthespack
tuxling
WEM97 [DONATE]
Think you have something to bring to the team? then contact me and we shall talk
What is this all about?/Why put this on my device?
This projects aim is to bring a range of linux distros to your android device through a method known as 'chroot', see it has running a linux distro within a virtual machine on your phone (Although its not! its using native ARM ports and the Android kernel) . You can access this virtual machine and run it on your phone without causing any damage to your device, or having to overwrite anything. Why might you want this? well my apps are designed to make the install and set up process as easy as possible while still giving you some flexibility. Once you have the distro up and running then you can pretty much run and install any linux software you like (so long as there is a arm port or it is not architecturally dependent).
Wait this uses VNC why shouldn't I just VNC to a computer?
VNC is used to access the GUI as at the moment I have not yet implemented a native way of viewing the GUI. But the Linux distro itself is running within the phone and can be controlled via the terminal app so if your a seasoned Linux user you may never even want to use the GUI
What is Chroot?/How does this work?
"A chroot on Unix operating systems is an operation that changes the apparent root directory for the current running process and its children" - http://en.wikipedia.org/wiki/Chroot
This method of running linux distros with android has been around for some time. I have worked on my scripts to make the process more user friendly and give you far more options from the word go.
The scripts start by mounting the linux image file within the android file system and then mounts the sdcard and if you have it internal memory within the linux file system.
Chroot is then used to change the root directory to that of the mounted linux and a bash shell is then opened to allow you to control linux this is kind of like 'booting' the OS.
The likes of VNC and SSH are then set up when linux is 'booted' to allow you to connect to the GUI if you require it.
Interested?
Ok so you want to get one of the support linux distros on your device, great welcome to the team
But first you will need to find out if your device is compatible with the method before anything else, this method 'should' work with pretty much any device but some ROM's/kernels will not work as they do not have loop device support etc.
HERE is a list of working devices and ROM's/kernels but remember just because its not on the list simply means no one has told me its working, it could still work!
Free Apps/Files
App
The App can be download via google play or the open source version can be download via source forge.
Distro Images
Below are our currently supported distros, click the distro of choice to go to its image download page on our source forge site (including torrent downloads)
Kali Linux
Donation keys
The donation keys allow you to support the project and unlock the configure menu within the launcher, this allows you to set and edit your VNC/SSH settings from within the app instead of on the command line!
This are also*available*to buy on the playstore or via paypal
Or if you donate more than £1 via paypal I shall send you a custom Donate key to unlock the extra features (if you donate more than £5 you will be added to the contribution list here and on the blog)
You can donate via paypal HERE Or my bitcoin wallet is: 13XxX4R2UFSkyCRyPMDXV1fT6VqzFi9d9T
Something not working?
Please first read through the FAQ pages HERE
Then if you still have issues check out the Q&A thread HERE. If you sitll can not find your answer, post in the that thread or email us [email protected]
Love the project?
Well there are plenty of places you can show your support, of cause you can buy the paid apps, but you can also 'follow' the project on a range of social networks and also keep up to date with news on the projects blog!
Main Site
Sourceforge Site (Where all the free apps files are kept )
Facebook page
Twitter page
Google+ page
IRC Channel = #linuxonandroid-dev (This is only for development not support!) #linuxonandroid-help (for help!)
banner for users of the project if you so wish to show your support by having the project in your signature.
If you would like to add this to your signature
You can simply add this code:
HTML:
[URL="http://forum.xda-developers.com/showthread.php?t=1585009"][IMG]http://zpwebsitefiles.com/images/loauser.png[/IMG][/URL]
Current Contributors
Project Developers
Zac Powell (myself) aka zacthespack
Martin Møller aka tuxling
William Means aka WEM97
App Translators
Marco Robles - Spanish Translation
Quentin Khan - French Translation
Stefanie Jung - German Translation
Ove Grunnér - Swedish Translation
Nikolay Suknyarov (NikolayS) - Bulgarian Translation
Other Contributors
Johan Vromans
Marshall Levin
Barry flanagan
Device Fund Donators (Those that donated to the device fund that ran from 26/08/2012 till 26/09/2012 and selected a perk)
scottlsteele
aceler
kailuuu
mja747
chrisindie
buki1
mharris867
never__sleep__again
joe95
jmoran1
fedebot
vichev.jordan
apadsethlang
1llu510n157lynx
innovateworld
karrth
AlexanderBalakersky
normenkdindiegogo
MORAZA.E7575
FilipJoelsson
brousch
igray78756
hawkinja
sullytrny
Donators (Those who have donated £5 or more to the project)
Davide Amatobene
Helder Carreiro
Aaron Coakley
Leo Barnard
Gregory Harrison
Chirado OHG
Infamous Webs
Matthew Collins
Rene Donker
David Marceau
Roberto Colistete Jr
cnbuff410
Javier Orozco
Jicaraca
Show me some screenshoots!
Ok ok heres a few screen shoots of the apps/distros in actions!
Change logs
App
Code:
11/04/2013
v2.3.1
*Added tip about changing screen size for VNC in Tips page
*Added permission for SuperUser
*Adjusted news layout
*Widgets are now resizeable (Android 3.1 and up)
*Updated translations for German, Spanish and Ukrainian
30/03/2013
v2.3
*Fixed bug that downloaded wrong fedora torrent
*Now building app against newest android version
*Included Kali Linux beta image for donation key users
*More force close fixes (thanks for the reports!)
23/03/2013
v2.2
*Included Fedora beta images for donation key users
*Removed Kickstarter widget, thank you to all those that donated!
*Updated Translation for Portuguese, Ukrainian, German and Norwegian
*Most force closes and crashes fixed!
21/02/2013
v2.1.1.1
*Fixed crash on startup
v2.1.1
*Code cleaned up and some of the experience crashes/freezes should be fixed
*Added kickstarter project to about page so you can keep track of progress!
*Added kickstarter project to the splash screen.
10/02/2013
v2.1
*Improved side menu with smaller text and better icons
*Fixed crashes when adding/editing images
*Fixed donation keys not working
*New Portuguese, Chinese translation
25/01/2013
*First bug fix, should take care of alot of the crashing (possible not all)
Please bear with us while we get to the route of these issues and iron out the new app.
If you do get any more crashes do please send in a report and let us know what you where doing when it crashed.
Thank you
24/01/2013
V2 Update!
Huge reworking of the app from the ground app, everything is optimised and new features including:
*Removed 'dashboard' UI in favour of a side opening menu to make switching between menu items much quicker
*Tabs used in Install guides to make moving through the install process easier (you can also swipe from tab to tab)
*New First 'boot' loading screen to give user information about what the app is doing on first boot, which stops freezing
*New way of handling donation keys should stop the app from not seeing a key when its installed (keys DO NOT need updating)
*Fixed ubuntu 10.10 linked to the wrong location
*Moved News to AsyncTask to stop it freezing
*Reworded All text to be easy to translate and fixed all grammar and spelling mistakes
*New File Manager to select image file in launcher
*Updated 1x1 widget to use file manager and improve its usability
*New Finnish, Danish, Korean, Norwegian, Ukrainian, Spanish and German translations
14/10/2012
*Includes new danish translation
*Change Ubuntu 10.10 links to there new location
11/10/2012
*Updated to include backtrack v10 image (See image change log)
01/10/2012
*Added French translation
*Added support for the custom donation keys from the indiegogo device fund
27/09/2012
*Removed old outdated translations
*Included new up to date Finnish and Italian translations
*Added a busybox reinstall option in the launcher menu, this will allow users whos busybox install fails to be set to executable to reinstall busybox
*Removed the device fund ad, we hit $600 and where able to get what we needed, thank you very much to all that donated
27/08/2012
*Changed news feed to our brand new website!
*Added Popup on first launch about our Device Donation Fund! (http://www.indiegogo.com/Linuxonandroid)
19/08/2012
*Fixed Archlinux downloads pointing to Debian downloads(Arch torrents and large image shound now download fine)
16/08/2012
*Allow creation of 1GB SWAP file for Donation users (kernel must support it)
*Added beta Archlinux images for Donation users (once out of beta will be avaible for all)
23/07/2012
*Added a popup window if the terminal app can not be found (the reason behind the app crashes when you try and launch linux)
16/07/2012
*Added 3 new buttons ready for future distros (have a look to see what the next distros will be ;) )
*Removed the links to the donation at the end of the guides
*Added small image 'ad' for the donation keys at the button of the install guides
09/07/2012
*New News section with a news feed right from the blog so you can keep up to date from within the app
*Bulgarian Translation added, thanks to Nikolay Suknyarov (NikolayS)
*Added links to donation keys at the end of the install guides (in free mode only)
03/07/2012
*Complete Linux Installer now free with 'donation' key apps
*App now checks for donation key and unlocks extra features if found (and passes validation)
*Extra features currently include Linux editor (to change screen size and mounts etc.)
11/06/2012
*Added a config screen on the launcher.
*Added a mount editor to the config screen where new mounts can be added.
*Added a option to turn on/off start of SSH and VNC servers.
*Added resolution settings to the config screen.
*Added auto run options, the image can now be mounted automatically when android has booted.
*Added Danish translations.
*The launcher now warn you if the image path is wrong and hide the config and start button.
*Changed the widgets and launcher to use a full image name instead of the path and script name.
*Fixed grammar and spelling for English text
*Added torrent downloads for debian and backtrack
07/05/2012
*Complete rebuild of app (looks the same but will make updates and change ALOT easier to implement)
03/05/2012
*Added torrent links and uploaded 1204 images to v2 and boot script to v7
*Added built in busybox so no longer need to install it yourself! (only working with 1204 v7 boot script, will work with other distros in next update)
*New changelog viewer, not much to see but it will be much easier updating it in the future.
20/04/2012
*Install guide updated to reflect the new Ubuntu images, and the fact that Ubuntu 12.04 is now stable
*Launch button and widgets updated to reflect the changes made in the terminal app (fixed bug that stopped widgets from working)
13/04/2012
*New onclick boot system that lets you set the location of your image file and boot script (so it no longer has to be in sdcard/ubuntu etc.).
*Brand new widgets that also let you set the location of your files
The new boot system was design by Martin Møller who kindly donated it to the project.
31/03/2012
*Includes install guide for Debian
*One click boot for Debian
*Boot widgets still not working will be fixed in next release
30/03/2012
*First release featuring all the features of the paid backtrack and ubuntu apps
Script
Code:
27/09/2012
*Fixed error with script not starting off using the apps busybox which causes errors on devices that dont have another busybox installed
16/08/2012
*Removed SU check, caused cut error on many devices
*Added support to create a 1GB SWAP file and use it
11/07/2012
*Fixed md5 sum file not deleting after checking
*fixed script not using the busybox built into the new app
11/06/2012
*Changed the script so it now look for any of our apps and use busybox from there. If none of the apps are found it will use /system/xbin/busybox instead.
*Changed the shutdown part to use the apps busybox, now it should shutdown for everyone.
*Now we write hosts and resolv.conf file only once when the image first boots. This allow changes to those files to survive restart of the image.
*Plus a lot of small changes to support the new config system.
03/05/2012 - Ubuntu v7 script
*md5 file checking if found in the same directory as the image (md5 file now included in zip of each image file) This can take some time to excute but will make sure the image is not currpt! (will only do it on first use once its checked the md5 file is deleted)
30/04/2012 - Ubuntu v7 script
*Improved error handling
31/03/2012
*Includes Debian boot script V1
Images
Code:
30/03/2013
Kali Linux
*New beta image for Kali linux
23/03/2013
Fedora
*New beta images for fedora
11/10/2012
Backtrack
*Fixed user not being able to use sudo
*Fixed S and M being used as keyboard short cuts
*Backtrack 5 wallpaper included again (by popluar demand!)
*Dare I say it Backtrack should now be completely stable
16/09/2012
Backtrack
*Fixed md5 miss match
16/08/2012
Backtrack
*fixed "error creating child process for terminal" when launching a terminal in backtrack
*Now asks for a password for VNC on first start up
*Removed some typoes in the script
ArchLinux
Core
*Updated to beta
*Internet working
*All updates and fully working pacman
Small
*All changes from Core included
*'Mostly' working vnc GUI
*LXDE Desktop included
*2GB file size
*Known Issues - LXDE dosnt render correctly, VNC does not let you change password, password set to 'backtrac'
Large
*All changes from Core included
*'Mostly' working vnc GUI
*KDE Desktop included
*3.5GB file size
*Known Issues - KDE# dosnt render correctly, VNC does not let you change password, password set to 'backtrac'
04/07/2012
*Debian and Backtrack images updated to fix user issues
11/06/2012
*It now asks if you want to start ssh and vnc at first boot and let you save the choices. (The complete installer app can change ssh/vnc start choices and change vnc resolution later, the free apps can do it by editing a file)
*Resolution and other settings are now saved the same place as the image itself so they are easy to edit. The file is called imagename.img.configs
*The permissions on /sdcard and /external_sd should be fixed now.
*Now the hosts and resolv.conf files are only written once, so changes the user make will now survive a restart.
*Plus a lot of changes to support the new config system, to many to mention.
03/05/2012
*Now boot using a normal user (called ubuntu), on first boot it will ask for you to set your own admin password for using running things as root. (thanks to barryflanagan for this!)
*Images now once again ask if you wish to save the screen size as default
*Ubuntu updated to newest updates
*Images include md5 files to check image
*+Plus possibly other tweaks I cant remember!
20/04/2012
*New Ubuntu 12.04 images. Core, small and full all updated to newest updates from ubuntus main stream
*Full image now include Unity desktop
*Firefox now working on both small and full images
31/03/2012
*Now includes Debian images (core/small/large) V1
I have this feeling you are about to be in high demand if all the ISC Webtop 3.0 videos are accurate. It's looks like Moto killed Ubuntu and replaced it with tablet mirroring mode.
BTW- Played with this on an Epic 4G and really like it. Could have used this last year for the Evo Desktop PC.
Lokifish Marz said:
I have this feeling you are about to be in high demand if all the ISC Webtop 3.0 videos are accurate. It's looks like Moto killed Ubuntu and replaced it with tablet mirroring mode.
BTW- Played with this on an Epic 4G and really like it. Could have used this last year for the Evo Desktop PC.
Click to expand...
Click to collapse
really? well thats interesting, bring them on, everyones welcome here
Runnin slow linux on android ? -> lets do Ultralight
Howdy, pardners!
I suggest ARM porting Puppy linux or some other other really light distro to gain maximum performace out of mobile device.
Also there ultra-light desktops . It seems that the best would be Ratpoison or Awesome. These are easy to incorporate into now available port of Ubuntu for android.
These should together provide fast and small display suitable linux env. for your mobile device!
see ya round!
mrWax said:
Howdy, pardners!
I suggest ARM porting Puppy linux or some other other really light distro to gain maximum performace out of mobile device.
Also there ultra-light desktops . It seems that the best would be Ratpoison or Awesome. These are easy to incorporate into now available port of Ubuntu for android.
These should together provide fast and small display suitable linux env. for your mobile device!
see ya round!
Click to expand...
Click to collapse
Yes I think your right, I will look at making my next support distro one of these amazingly light distros, get the most power we can our of our devices
In your opinion, which of these distros is the fastest? I have a single core device so need all the help I can get lol
Sent from my SAMSUNG-SGH-I997 using xda premium
dustinhayes93 said:
In your opinion, which of these distros is the fastest? I have a single core device so need all the help I can get lol
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
either ubuntu 12.04 with lxde or debian i would stay away from gnome it takes alot more memory . At the moment i love debian its my 'daily drive'
Sent from my GT-N7000 using xda premium
zacthespack said:
either ubuntu 12.04 with lxde or debian i would stay away from gnome it takes alot more memory . At the moment i love debian its my 'daily drive'
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Debian it is! Btw thanks for your work. Its amazing seeing full desktops in your pocket... Amazing work!
Sent from my SAMSUNG-SGH-I997 using xda premium
I got Debian to work on a Huawei U8800 Ideos X5 with the Aurora 2.0.4 ROM.
Everything was running smooth and great, but then I logged out from the system to see if I could switch DEs.
From there, all I saw was the wallpaper of the desktop and nothing else.
I exited with the terminal and tried again. Now I get this message:
VNC connection failed!
failed to connect to localhost/127.0.0.1 (port 5900):
connect failed: ECONNREFUSED (Connection refused)
Click to expand...
Click to collapse
Is there any way I could reset the cache and try everything again?
ALSO, after the sh-ing debian.sh, this is what I get:
Loop device exists
mount: mounting /dev/block/loop255 on /data/local/mnt failed: Device or resource busy
mount: mounting /sdcard on /data/local/mnt/sdcard failed: No such file or directory
net.ipv4.ip_forward = 1
Debian is configured with SSH and VNC servers that can be acessed from the IP:
eth0: No such device
vncserver: geometry 800x480 is invalid
Starting OpenBSD Secure Shell server: sshd.
Click to expand...
Click to collapse
It was different than before, so I thought this would be useful information.
I have no idea what to do at this point.
Andrioid. said:
I got Debian to work on a Huawei U8800 Ideos X5 with the Aurora 2.0.4 ROM.
Everything was running smooth and great, but then I logged out from the system to see if I could switch DEs.
From there, all I saw was the wallpaper of the desktop and nothing else.
I exited with the terminal and tried again. Now I get this message:
Is there any way I could reset the cache and try everything again?
ALSO, after the sh-ing debian.sh, this is what I get:
It was different than before, so I thought this would be useful information.
I have no idea what to do at this point.
Click to expand...
Click to collapse
Hmmm looks like you broke vnc I would recommend reinstalling vnc do apt-get remove tightvncserver then apt-get install tightvncserver
then do a restart of your device and try again.
If you want to use a different desktop you need to configure it in in /root/.vnc/xstartup vnc dosnt run right if you log out of a session and thus is broke, didnt think vnc even let you log out but guess it will
zacthespack said:
Hmmm looks like you broke vnc I would recommend reinstalling vnc do apt-get remove tightvncserver then apt-get install tightvncserver
then do a restart of your device and try again.
If you want to use a different desktop you need to configure it in in /root/.vnc/xstartup vnc dosnt run right if you log out of a session and thus is broke, didnt think vnc even let you log out but guess it will
Click to expand...
Click to collapse
Reinstalled vnc, rebooted phone, still not working.
the speed and responsiveness of debian on a nook tablet / cm7 is great!
however, is there any way to get flash installed/working on debian's iceweasel?
what i was wondering is only, hows the battery?
as far as my lofic go, ubuntu on laptop is a battery drain.. and how if its running on a phone that majority has lower capacity of battery
Andrioid. said:
Reinstalled vnc, rebooted phone, still not working.
Click to expand...
Click to collapse
Hmm ok you might have to try using a new image?
con_ritmo said:
the speed and responsiveness of debian on a nook tablet / cm7 is great!
however, is there any way to get flash installed/working on debian's iceweasel?
Click to expand...
Click to collapse
flash is not working very well on ARM linux, I do not think there is a official port and other 3rd party trys dont work well
Bilgets said:
what i was wondering is only, hows the battery?
as far as my lofic go, ubuntu on laptop is a battery drain.. and how if its running on a phone that majority has lower capacity of battery
Click to expand...
Click to collapse
really battery life not much more used than any other app running the whole time, of cause if you use the GUI none stop it will drain more but you should still get alot of life
zacthespack said:
Hmm ok you might have to try using a new image?
Click to expand...
Click to collapse
Awesome! It worked! Thanks!
Is there any reason to get the complete linux installer for €2.40?
Andrioid. said:
Awesome! It worked! Thanks!
Is there any reason to get the complete linux installer for €2.40?
Click to expand...
Click to collapse
well it includes faster downloads of the files from a server not just source forge, you can boot by clicking a button in yhe app so no more typing commands, you will get all future distros and updates first and the best bit is you get this amazing feeling for helping a developer keep releasing amazing stuff (if i do say so myself )
Sent from my GT-N7000 using xda premium
zacthespack said:
well it includes faster downloads of the files from a server not just source forge, you can boot by clicking a button in yhe app so no more typing commands, you will get all future distros and updates first and the best bit is you get this amazing feeling for helping a developer keep releasing amazing stuff (if i do say so myself )
Click to expand...
Click to collapse
Alright. I was just wondering if I'm missing out on something. Unfortunately I can't donate. :/
Anyway, here's a picture of Debian running on my phone:
Andrioid. said:
Alright. I was just wondering if I'm missing out on something. Unfortunately I can't donate. :/
Anyway, here's a picture of Debian running on my phone:
Click to expand...
Click to collapse
thats quite alright so long as you enjoy the app etc then my work here is done
Sent from my GT-N7000 using xda premium
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1.2 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
{
"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"
}
Code:
#include <std_disclaimer.h>
/*
* Your 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 features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
This thread is for Official LineageOS 14.1 builds for chagallwifi (SM-T800) The following will not be supported here:
Custom kernels
Mods
Xposed
I don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Have not attempted a clean flash
First time flashing LineageOS 14.1 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Install the Google Apps addon package (Optional)
Reboot
Make sure you have the Marshmallow bootloader. Guide is in the comments below.
There will be a new build every week, every Monday.
The builds will no longer be personally tested by me before being uploaded (but everything will probably be fine)
Change logs will no longer be posted within every new build, but instead when the changes are uploaded to GitHub. I will try though to post changes for major bugs or fixes as they are released.
Some builds might feature only minor changes, ie. only updating the LineageOS source
Chagallwifi Download
Google Apps:
Beans GAPPS 7.1.2
Kernel
https://github.com/LineageOS/android_kernel_samsung_exynos5420
Device Tree
https://github.com/LineageOS/android_device_samsung_chagallwifi
Aytex, who made all of the banners on this post.
@Barracuda77777 (For helping along the way)
@UpInTheAir for his kernel magic and misc fixes
@crpalmer (for picassowifi device and kernel gits - the base @Barracuda77777 and @nvertigo67 started of from)
@eousphoros (for his device git)
@nvertigo67 (for his work on chagallwifi)
@Nexorrr (for his work on chagalllte)
Fingerprint is disabled
Other issues?
Before posting in this thread, make sure of a few things:
You used the search function of the forums.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread.
Logs! You can use this: https://play.google.com/store/apps/details?id=com.tortel.syslog
For OTA updates to flash correctly:
Update your TWRP to 3.1.0-1 (USE THE 2017-05-04 BUILD OR LATER. DO NOT USE A BUILD FROM BEFORE THIS DATE)
You can get Official TWRP 3.1.0-1 for chagallwifi from this link!
TWRP for CHAGALLWIFI
This updated TWRP recovery image contains a fix that will allow it to flash OTA updates properly!
How to update to Marshmallow bootloader (required for 20170324 and later builds)
Updating the bootloader is very quick and doesn't wipe data or repartition the device.
If the last Samsung ROM you had was 6.0.1 Touchwiz, you already have Marshmallow bootloader and don't need to follow these steps. (If you were on MM, and it still won't boot, follow the steps below)
1. Download the bootloader-only Odin package: T800XXU1CPK2.tar.md5
This has the latest Marshmallow bootloader (December 2016)
https://www.androidfilehost.com/?fid=457095661767146298
2. Download Odin 3.11
You can skip this if you already have a working Odin
https://www.androidfilehost.com/?fid=673368273298937183
3. Shutdown your tablet and start it up by holding Power+Home+Volume Down to enter Download Mode. Volume Down is the one right next to the power button. Really shut it down and use this key combination, if you use Advanced Restart, or go into download mode via TWRP the bootloader won't change.
4. Make sure the screen of your tablet has a green android symbol with a "Downloading..." text
5. Open Odin3_v3.11.1.exe and follow the instructions in this image:
If anything is missing, you WON'T flash bootloader successfully.
6. Click Start. Your tablet will automatically reboot back into your ROM.
7. To verify you have the new bootloader, you can run in terminal emulator "getprop ro.bootloader". It should say T800XXU1CPK2.
Thanks @ZakooZ for the post!
Deathly Adiutor App
Deathly Adiutor is an open-source, modified version of Kernel Adiutor made specifically for Exynos 5420 devices.
Features
Power Saving:
S-Pen Power Saving - Same as in Touchwiz, disables S-Pen detection if it's inserted in the slot
S-Pen Input Booster - Instantly increase CPU frequency when the S-Pen touches the screen
Touchscreen Input Booster - Instantly increase CPU frequency when you touch the screen
Touchkey Input Booster - Instantly increase CPU frequency when you touch the capacitive buttons
Touchscreen Glove Mode (Not all screens support this)
CPU Control:
CPU Settings reworked - Deathly adiutor back-end was cleaned up to work specifically with our CPU
CPU Thermal - Control all thermal throttling points for the CPU (make your device run colder... or even hotter)
GPU Control:
GPU Time in States - Same as CPU Time in States (Times in each frequency)
GPU Frequency Control (not yet supported on Nougat)
GPU Voltage Control (not yet supported on Nougat)
GPU Governor Control (not yet supported on Nougat)
Battery control:
Full power statistics - See current and maximum charging currents and current source of power
Unstable power source detection - Lowers current until the power source is stable
Customize charger current limits - Make your device charge faster (safe, if the charger can not supply enough current, the board will dynamically decrease the current)
Screen-On current limiter - Limit charging if screen is on (to avoid overheating)
Speakers:
Privacy mode - Disable main speaker if headphones are plugged in
Earpiece volume
Left/Right speaker volume
Speaker equalizer
Headphones:
Left/Right channel volume
Mono output mode
Headphone equalizer
App Themes:
Light theme - White and Red
Dark theme - Grey and Red
Credits
This post was written by @ZakooZ
This app is brought you by the exynos5420 developer team: @deadman96385 @thompatry @ZakooZ @Orion116 @mosimchah @joshndroid @Andmoreagain @thermskin, @javelinanddart, @tincho5588, @ShevT @DarkExistence
Translators:
@ShevT - Russian
The following people deserve distinction for their major contribution:
@tincho5588, responsible for 80%+ of the code for the new features
@deadman96385, the main maintainer of the Deathly kernel and most of the remaining code
Downloads
The app can be found in the Play Store:
Free version (with ads): https://play.google.com/store/apps/details?id=com.exynos5420.deathlyadiutor.ads
Donator version (no ads): https://play.google.com/store/apps/details?id=com.exynos5420.deathlyadiutor.adfree
Helping the developers
You may have noticed there's 2 versions of this app, one ad-free for donators and one with ads.
You can help us by clicking ads you're interested in for the free version, or purchasing the donator version!
We will use the money generated by this app as common money for the developers of the team. It will be used to pay for our web-hosting (we own a gerrit server and a domain name, exynos5420.com). It will also be used to buy a new device if one of ours breaks.
Translating the App
You can also help us by translating the app to your language:
1. You can start by looking at the full english language file: Link
2. Then compare it to your unfinished language file. You can find it here, under values-xx/strings.xml, xx being your language abbreviation.
3. You can then fill-in the missing strings in your language file. Here's an example of what a proper update looks like.
4. Then you can submit your translation by using our gerrit. If you don't know how to use gerrit, just PM the translation to your favorite developer and he'll get it merged!
Thx for your work
Looking forward to testing it out
Thank you very much for your work!
It doesn't works for me, I only see boot animation and it doesn't start even after 20 minutes. I tried Paulicat version and works fine. Whi? I did a clean flash.
Same for me. Bootllop after flashing ROM and latest Gapps (nano).
Yeah, bootlooping.
BananaPrime said:
Yeah, bootlooping.
Click to expand...
Click to collapse
I installed with a full wipe (including internal sdcard), using latest pico gapps.
No issues...
I also recently updated my bootloader to Mashmallow, but I doubt that's what makes mine bootup while some bootloop.
Bootlooping? How far does it boot ?
Please be 100% certain that you wiped dalvik, system, data and cache in twrp and try flashing without gapps. Did you change anything such as flash custom kernels etc?
Could one of you take a logcat during boot for me please. It has to be user error seeing as mine is working fine, and others are working fine. The number of downloads - complaints shows that.
Just plug your tablet into you PC while it's booting (make sure you have adb installed)
Then , once you start to see the screentype adb logcat into your terminal (./adb logcat if windows or Linux)
Thanks
Just upgrade from @Paulicat's Jan 17th build to this Jan 25th build; just flashed lineage, open gapps nano and SuperSU (in that order, in one go) and rebooted.
Looks like the video problems of the previous release are not present here; I can now play YouTube Videos at high res and use the HW codecs of MX Player without stuttering; previously I had to drop from 1080p to 720p or use the MX+ codecs to make it play smooth.
The WebView component apparently still have problems; using for instance FlipBoard to read articles causes a crash/weird screen flickering from time to time, associated with a crash. The log reports a WebView crash (there's first a "OpenGLRenderer: GL error: Out of memory!" followed by a google-breakpad dump of "WebView:55.0.2883.105" "A arm 04 armv7l samsung/lineage_chagallwifi/chagallwifi:7.1.1/NMF26V/e609fadfba:userdebug/test-keys" "webview" "OpenGL ES 3.0|ARM|Mali-T628" and a long hex dump.
Finally, GPS does not work out of the box; the gpsd still misses a few libraries. I've copied them from elsewhere (RR, if I recall correctly) and have placed libsec-ril.so and libxml.so in /system/lib -- and then GPS works instantly (as far as I can tell it may lock on faster than on the previous build).
I guess the WebView has to be fixed upstream, but maybe the missing gps related libraries could be included in the next build?
Thanks for your great work!
- Per.
pnomandk said:
Just upgrade from @Paulicat's Jan 17th build to this Jan 25th build; just flashed lineage, open gapps nano and SuperSU (in that order, in one go) and rebooted.
Looks like the video problems of the previous release are not present here; I can now play YouTube Videos at high res and use the HW codecs of MX Player without stuttering; previously I had to drop from 1080p to 720p or use the MX+ codecs to make it play smooth.
The WebView component apparently still have problems; using for instance FlipBoard to read articles causes a crash/weird screen flickering from time to time, associated with a crash. The log reports a WebView crash (there's first a "OpenGLRenderer: GL error: Out of memory!" followed by a google-breakpad dump of "WebView:55.0.2883.105" "A arm 04 armv7l samsung/lineage_chagallwifi/chagallwifi:7.1.1/NMF26V/e609fadfba:userdebug/test-keys" "webview" "OpenGL ES 3.0|ARM|Mali-T628" and a long hex dump.
Finally, GPS does not work out of the box; the gpsd still misses a few libraries. I've copied them from elsewhere (RR, if I recall correctly) and have placed libsec-ril.so and libxml.so in /system/lib -- and then GPS works instantly (as far as I can tell it may lock on faster than on the previous build).
I guess the WebView has to be fixed upstream, but maybe the missing gps related libraries could be included in the next build?
Thanks for your great work!
- Per.
Click to expand...
Click to collapse
Glad most things is working for you!
Yep, this build has a more updated device tree then what Paulicat had so there are a few fixes!
GPSD is being investigated by @deadman96385 and should be an easy enough implementation
Thats the first time I have heard about the webview implementation, would you mind sending a full log? Thanks for letting us know!
DarkExistence said:
Glad everything is working for you!
Click to expand...
Click to collapse
So far, it's better -- also appears more "smooth" and fluid in use, I think
GPSD is being investigated by @deadman96385 and should be an easy enough implementation
Click to expand...
Click to collapse
Yep, possibly just a few missing libraries or a different linking method, or something. Good you're working with @deadman96385 on this also; he already responded to this in the other thread when I debugged and reported it related to the previous build.
Wiped all for 3 times, it doesn't boot.
Eboshi Moriyama said:
Wiped all for 3 times, it doesn't boot.
Click to expand...
Click to collapse
I have a f2fs data partition. Perhaps that ist the reason for the bootloop?! (i have the bootloop too)
Clean flash - boot OK - flashed pico OK - flashed superSU OK - boot OK
No prob at all :good:
kaodd said:
Clean flash - boot OK - flashed pico OK - flashed superSU OK - boot OK
No prob at all :good:
Click to expand...
Click to collapse
tried again with clean ish flash - bootloop
tried dirty over RR 7 - boot ok - total frozen :laugh:
start with 3-fingers in recovery, u know what i mean
starting again lineageOS Darky-Edition
nice boot animation, kinda posh will try xposed too
My T800 is currently happily running the now out of date [AOSP 7.0][T700/T705/T800/T805] by @Schischu so I'm looking to upgrade. Here are apps I'd like to know work before I give this ROM a try. If anyone can tell me if they work or not I'd appreciate it. If any of them are considered mods I apologize in advance as I've read the OP mods policy. In any case I'd never ask for their support or inclusion in the ROM as that's my responsibility.
Here's my list:
Viper4Android
Substratum
LastPass (some other 7.1.1 ROMs have issues with this app)
Netflix
Plex
Thanks
{
"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"
}
Jump to...
ROM Index (#2) | Kernel Index (#3) | Changelog (#4)
Whaddup, XDA? ^_^
This began as a modest little post, aptly named Post#3333 in the Resurrection Remix thread to help keeping the thread clean. Many thanks to @varund7726 for his support and making it the official RR Bacon FAQ!
It gained more attention than I thought it would so I decided to make a more general version in a dedicated thread.
This is not my work but a collection of answers by amazing people that roam these digital lands. Of course, I do appreciate you clicking that Thank you button . I hope people looking for answers will find their way here. If someone has any input, feel free to drop it in the thread or send me a PM and I'll update the post if needed. It may be best to not ask new questions here, you'll find more satisfying answers in the appropriate threads of the custom ROM you're using or in the general Help thread.
Now, let's get this out of the way first:
Code:
What are you reading this for? There isn't a single Bacon owner with valid warranty anymore. Anyway, here's the original disclaimer:
You have the [U]right[/U] to unlock your device, not the [U]obligation[/U] to do so.
Anything you flash can and will be used against you in a court of technical dispute.
If you get your device bricked, you will [B]not[/B] be provided with a new one.
If your mother in law disappears as a result of something mentioned in this thread,
I will happily take your donations to thank me but I will not be held responsible!
Mind that this is – and probably will continue to be – a work in progress.
This is an attempt to collect general solutions, which will not always work in every case.
Please DO NOT QUOTE THIS ENTIRE POST! Thanks.
▂▃▅▇█▓▒░INDEX░▒▓█▇▅▃▂
New items are indicated with
; Updated items are indicated with
GENERAL
How can this FAQ help me? Why did you make this?
Why isn’t anyone helping me?
Creating a logcat
PREPARING
EXT4 vs. F2FS
What else do I need? (Prerequisites)
C6 or C7, which is the best firmware? (troubleshooting network issues)
What kernel should I use?
FLASHING
Installing TWRP
How to flash (with links!)
I'm seeing two red errors in TWRP while flashing
I'm getting an error while flashing Gapps
I dirty flashed and something doesn't work anymore
CRITICAL
My screen is going black, I can only see notifications
My device just exploded!
The other person (nearly) can't hear me during a call
I have another audio/microphone problem
Can't read or write to internal storage (/sdcard)
QUICK FIXES
The camera app can't connect to the camera
Google Assistant isn't working or "OK Google" detection fails
QS toggle 'drops' when trying to add it
OTHER
How do I apply themes and which ones can I use?
Fast/Quick Charge isn't working
MODS
ViPER4Android
Camera mods
1. GENERAL
1.a. How can this FAQ help me? Why did you make this?
My goal is to maintain a one-size-fits-all thread where people can find answers to the most common current problems for the OnePlus One a.k.a. Bacon. It also serves as a detailed guide through the flashing process. The reason I'm doing this is threefold: 1) Despite the fact that this is a 2014 device, the 1+1 community is still booming. Best proof of that is that our very own Bacon is by far the most popular device for LineageOS with currently over 80,000 installs! I'd love to honor that fact. 2) This is my first support thread, I hope to learn a great deal from it. 3) I honestly enjoy helping people =)
1.b. Why isn’t anyone helping me?
Keep in mind that XDA is not your personal tech support. The idea is that we help each other as a community, not to expect an immediate answer to your problem. If you do not add any useful technical information to your query, your post may not be considered, this is even more so the case in development threads.
There are three ways (that can be combined) to achieve a technically sound post:
Attach a logcat! See 1.c. on how to do this.
Provide screenshots, especially handy with aesthetic issues.
Provide the exact steps to reproduce the problem (be VERY specific).
Tip: use the time that you’re waiting for an answer to find it yourself. If you managed to resolve it yourself, follow-up on your own post and explain how you did it, it may be helpful to other users in the future.
1.c. Creating a logcat
This'll only take a minute and may provide invaluable information for any developer or someone trying to help. There are a number of ways to create them, this tutorial explains a remote technique. I do believe this is the easiest way:
Download CatLog from the Play Store
Make sure you have a dedicated 'menu' button (CatLog is old skool)
Run the app, give it root rights, [optional] pause the current flow with the pause button and then clear the window tapping the circle with the X in the middle top right (this will provide peace of mind, the constant stream can be a bit overwhelming)
Tap the menu button, press Record followed by OK. Any activity is now being recorded
Press your home key and launch the app that's giving you trouble, let the crash happen and repeat it a few times
Drag down notifications and tap the cat, it'll state "select to stop recording"
CatLog will now show you what it has recorded, use the search feature to check if no privacy sensitive information (your e-mail, a phone number etc.) has been collected, you can edit this out manually with a text editor if needed
You can simply tap the menu key again and select Send to share the log, this feature will also add device info (brand, model, Android version ...)
If you'd like to share it manually or want to make some edits first, you'll find the file in [internal storage]/catlog/saved_logs
2. PREPARING
2.a. EXT4 vs. F2FS
A lot can be said about filesystems but I won't go into any technical debates on here. The main difference boils down to this:
F2FS is arguably faster than EXT4; EXT4 is arguably more stable than F2FS.
In real use performance, not much difference will be noticed in terms of speed. Since the release of Oreo for Bacon, however, stability on F2FS has decreased drastically or it is unsupported entirely. If you have never changed this yourself, the system will most likely be formatted to EXT4. You can check with DiskInfo or in recovery. In case you want to run Nougat on F2FS or you want to return to EXT4 but forgot how, here's a refresher:
In recovery, go to Wipe > Advanced Wipe
Select a single partition
Tap “Repair or Change File System” (if you see “Invalid partition selection” appearing, it means the partition’s file system cannot be changed
On top you can see the current file system, tap “Change File System” followed by the one you want (stick to either EXT4 or F2FS)
Swipe to confirm
I found this XDA article (interview with Francisco Franco) quite interesting on this topic.
2.b. What else do I need? (Prerequisites)
A good working TWRP
The ROM zip of your choosing
Gapps (ARM/8.1/nano, there are plenty alternatives, check with your ROM maker which one is advised)
last CM13 snapshot (only if you didn't have CM13 before)
You should place all downloaded files in the root of your internal storage (/sdcard). It's stongly recommended to check md5 hashes! In case of Gapps, download the md5 checksum file and place it together with the zip.
2.c. C6 or C7, which is the best firmware? (troubleshooting network issues)
None. There are mixed results on both, depending on which network(s) you use. Which one works best for you? The only way to find out is by flashing one of the three versions below (that differs from your current version, check under About phone > Baseband version. The recommended one for most users is C6-00241 (the most likely one you currently have).
Here are three very common firmwares and a Frankenstein release:
Download DI.3.0.c6-00241
Download 4.0.1.c7-00013 (2016)
Download 4.0.1.c7-00011 (2016)
@MrSHME's Frankenstein Release
[instructions and credits]
There's a whole load of them available in this thread. I've done some elaborated testing there, read my findings here.
Important note when flashing firmware: backup your modem and EFS partitions first! It may happen that the system hangs in boot animation after a firmware flash (I experienced this a few times). Give it some time and it should automatically boot back to recovery. In recovery, reboot back to system (don't do any wiping or anything) and it should boot just fine. If the system keeps hanging for over 20 minutes, manually force a shutdown (long press power) and try booting regularly again. Still no luck? Boot to recovery and flash other firmware or restore your modem backup.
2.d. What kernel should I use?
You don't have to use any. Want to take the plunge anyway? Sure, check out post #3 for a list. You can make a backup of your kernel/blobs with Flashify
Read (much much) more about tweaking in this excellent guide by @Saber
3. FLASHING
Always make a nandroid backup before you flash anything!
3.a. Installing TWRP
Before flashing anything, make sure you are using a compatible TWRP! You'll find a download link to the one I'm using in this FAQ, I'll keep it updated. I know this is basic information but to avoid any mistakes, I'm providing all needed steps:
Download a TWRP .img file
Move it to the adb (official download) folder where adb and fastboot exe's are located
[this is no requirement but let's do this for the clarity of these steps] rename it to recovery.img
Reboot device into fastboot via advanced reboot menu, 'adb reboot bootloader' command or – if the device is off – press and hold "Power + Volume UP" until "Fastboot Mode" appears
Setup the correct drivers and connect the device to the PC/Mac
Open a command line (terminal on Mac I guess) in the adb folder
type "fastboot devices" to see if the system picks up the device
type "fastboot flash recovery recovery.img" to flash TWRP
Disconnect the device from the PC
Press and hold power until the device turns off
Hold "Power + Volume DOWN" to boot into the newly flashed TWRP recovery
3.b. How to flash
Always make a nandroid backup before you flash anything!
Clean Flash:
In TWRP, wipe by swiping factory settings. If you're experiencing issues, it's best to do a full wipe (Advanced > select System + Data + Cache + Dalvik-ART Cache)
[optional] Flash last CM13 snapshot and do another full wipe. This step is crucial when you've never been on CM13 before. This flash will fix/prevent a wide variety of issues! You only need to do this once.
Flash the ROM zip
[optional] Flash a custom kernel
Flash Gapps (ARM/nano, version should be the same as ROM), check Gapps compatibility in ROM thread.
[optional] If root is desired, flash Magisk (stable or beta)
[optional] Flash other mods
Wipe Cache/Dalvik-ART Cache and reboot
Dirty Flash (update):
Reboot to TWRP
Flash the ROM zip
Wipe Cache/Dalvik-ART Cache and reboot
Semi-Dirty Flash:
This is basically the clean flash procedure but you backup the /data partition before wiping and restore it afterwards (or don't wipe /data at all). I do not recommend this method.
Example (my flashing procedure for a specific Oreo ROM):
Download ROM and Open Gapps to root. Check ROM md5 hash with MiXplorer
Backup all user apps + a few system elements (messages, call logs etc.) with TitaniumBackup (+pro key)
Copy the TitaniumBackup folder to my PC
Reboot to latest TWRP, create Nandroid backup of System and Data (sometimes copy that one to PC as well)
Wipe /system + /data + /cache + /art-dalvik cache
Flash ROM + Gapps + OP5 camera mod + iYTBP + Magisk beta (all in one go), wipe caches after flashing and reboot
I let Google setup install all apps, then restore app data with TiBu, this feels more clean
Restore system elements with TiBu + apply AdAway lists + restore Android ID (for my banking app) and reboot
Enjoy awesomeness!
This seems like a lot of work but it doesn't take more than an hour. Since releases are currently pretty far apart, it's only a small effort for many days of smooth sailing. If release frequency would increase, I wouldn't make a Nandroid and wouldn't copy everything to PC every single time. If I don't have Wi-Fi for some reason, I restore all apps + data with TiBu instead of using Google setup.
3.c. I'm seeing two red errors in TWRP while flashing
They are LOS related and have no effect on the flash procedure, don't worry about it, you can safely ignore them.
3.d. I'm getting an error while flashing Gapps
Error 70: You're trying to flash a package that is too large such as Stock. Try a smaller package.
Error 64: Wrong architecture, you need an ARM package, not ARM64/x86/x86_64.
Error 20: Wrong version, you need 6.x for Marshmallow, 7.x for Nougat
3.d. I dirty flashed and something doesn't work anymore
Please do not inquire about issues after (semi-)dirty flashing. The first step for you to take is to perform a clean flash. If the issue is still present and it hasn't been posted before (PLEASE use search!), then post your inquiry in the ROM thread.
4. CRITICAL
4.a. My screen is going black, I can only see notifications
This behavior is caused when a profile has lock screen disabled. The only way to recover from this condition is to clean flash, or restore a backup that was made prior to setting up the profile. It may be possible to reboot successfully if one is in a location or situation that triggers a profile that doesn't have lock screen disabled, then change the problem profile settings (unconfirmed).
4.b. My device just exploded!
It's most likely unrelated to a software problem but please, feel free to share pictures!
4.c. The other person (nearly) can't hear me during a call
Can't be heard
In /system/build.prop, change
ro.qc.sdk.audio.fluencetype=fluence
to
ro.qc.sdk.audio.fluencetype=none
Edit /system/etc/audio_platform_info.xml (in Oreo this file moved to /system/vendor/etc)
<device name="SND_DEVICE_IN_HANDSET_MIC" acdb_id="40" />
to
<device name="SND_DEVICE_IN_HANDSET_MIC" acdb_id="4" />
Audio comes out low
remove
ro.qc.sdk.audio.fluencetype=fluence
change
persist.audio.fluence.voicecall=true
persist.audio.fluence.voicerec=false
persist.audio.fluence.speaker=false
(flashable version)
Reboot.
Still having problems? Test your sensors and mic more thoroughly with an app like this, there may be a hardware failure. Before opening her up, you can do a last software check by trying another ROM or by returning to 100% stock.
4.d. I have another audio/microphone problem
Please refer to the OnePlus One Audio Mods Collection, a genious collection of all sorts of fixes and workarounds to achieve fully featured audio on the OPO.
4.e. Can't read or write to internal storage (/sdcard)
Your /sdcard partition is most likely corrupt! Now what? When this happens to /system or /data we can simply perform a clean flash. Wiping our internal storage, however, means wiping a lot of precious data that is not included in a Nandroid backup so it's crucial to make regular backups manually. A lot of trouble can be avoided with cloud syncing (Dropbox, Google Photos, etc.). When read/write errors present themselves (camera can't save photos, not enough space errors while there's plenty, folders disappear, etc.) it's important to work fast before all your data becomes unavailable indefinitely. Here's how you can reset your internal storage in a non-destructive manner:
Copy the entire content of your internal storage (/sdcard) to an external location (PC or OTG drive). Make sure the real important things are immortalized (e.g. your cat photos/videos are synced with Google Photos and/or are trending on YouTube)!
Reboot to TWRP
You may want to create a nandroid backup at this point but do not forget to copy the backup to your PC or make the backup via OTG as we're about to wipe the internal storage (and with it, all internal backups)
Go to Wipe > Advanced and select only Internal storage, confirm to wipe (you may experience some discomfort at this point, this is normal)
Reboot to TWRP (from recovery to recovery, that's right)
Now copy all content back from the folder on your computer to the internal storage. You should be able to do this simply over USB while TWRP is active. If you don't, go to the main TWRP menu, tap 'Mount' followed by 'Enable MTP'
When the copy is complete, reboot to System and your trouble should be gone!
We're doing the wipe AND the restore inside recovery because if you would boot your device with an empty /sdcard partition, the Android system and all running apps would start freaking out and get going on all sorts of crazy, recreating their folders and files.
Tip: this is the perfect opportunity to sieve through those files! I recommend not just copying everything back but only the things you still need. Exclude folders of apps that aren't installed anymore and skip unused media files. This will decrease the chance of future corruption. Take some time to make your internal storage shipshape!
5. QUICK FIXES
5.a. The camera app can't connect to the camera
If you flashed something like OxygenOS Blobs, your camera will not work unless you set SELinux to Permissive. You should find this in your ROM settings (e.g. for RR this is under Settings > Configurations > Miscellaneous > Selinux mode > Permissive) or you can easily do this with SELinuxModeChanger.
Why this is a bad idea: SELinux or Security Enhanced Linux prevents malicious apps from gaining unlimited system level access by exploiting security holes. By setting it to Permissive, you’re disabling this extra layer of security. Infections due to this are rare but do happen, you’ve been informed.
5.b. Google Assistant isn't working or "OK Google" detection fails (this may be obsolete by now, please notify me if it is)
See 4.c., “Audio comes out low”.
5.c. QS toggle 'drops' when trying to add it
This may happen when attempting to add one of the lower QS toggles. There are two ways to work around this bug:
By lowering the display size: go to Settings > Accessibility > Display size (or under custom ROM configurations) and change it to Smaller or Smallest
By messing around: move icons from the top to the QS panel until you're able to slide the QS toggle you need without 'dropping' it
This video shows it works fine:
6. OTHER
6.a. How do I apply themes and which ones can I use?
OMS compatible ROMs only! To start, install Substratum from the Play Store, open it and grant it root rights (both substratum and masquerade). Then search the Play Store for substratum themes that are compatible with your Android version. Some will cost you something but most are really worth it and there are some great free ones as well. After installing a theme, apply it in Substratum. Don't forget to read the theme creator's instructions, some combinations can cause trouble!
6.b. Fast/Quick Charge isn't working
That's because the OnePlus One doesn't support it. You can, however, tweak charging rates with kernel tweaks (which is still limited, don't expect dash charge speeds). Equip yourself with proper hardware. A ‘smart’ charging station and quality cables can go a long way. Mind that faster charging is not better charging per se. You may shorten the lifespan of your battery when pushing it to the limits. Charging with the official charger/cable (which should take about 2 hours from 0 to 100%) is still the best way to treat your battery. Also note that if you got your device back in 2014, there's a good chance your battery doesn't have its full capacity anymore, longer charge rates and shorter lifespans can be expected. That being said, the OPO was equipped with a kickass quality battery, even after abusing it for all these years, many users have reported it still works great!
7. MODS
7.a. ViPER4Android
Since Magisk is more widely adopted, installing V4A has become very easy.
In Magisk Manager, tap the three lines top left
Tap Downloads
Scroll down to ViPER4Android FX and tap the download icon
Tap Install followed by Reboot
Once booted, go into Magisk > Downloads again
ViPER will now be on top, tap it
You'll find a link to the latest APK, download and install it
That's it. Open it and change all the settings you want, then reboot once more to make sure it all runs fine.
7.b. Camera mods
The OnePlus 5 camera software has been ported (download here) to Bacon and it works great, this is my current favourite.
Great camera mod: CameraNextModV2. It's just a simple flash away.
Not much of a mod but a Camera app optimized for our OPO: Bacon Camera!.
And good to know: Google Camera 4.1.006.135988111 is the last compatible version for Bacon.
Thank you for contributing, @venky716 @bdwilk @Baldesarra @Mr.Ak @Silverview @abhi08638 @tazzkiller @Genericxx @Turpb (PM me if your name should be here!)
Bacon ROM INDEX
For your convenience, I've listed *most* (maybe all of them, who knows) Nougat+ Bacon ROMs below. Please feel free to post in the thread if you found one not mentioned below. Cheers!
Original Android Development
PIE!!!!!
[ROM][9.0.0_r3] POSP v2.0 - BETA [OFFICIAL]
Oreo
[ROM][8.1.0_r29] AOSP Oreo for OnePlus One [Discontinued][23/05/2018]
[ROM][OPO][8.1.0_r43] Candy8.1 [OFFICIAL][SUBS]
[ROM] [UNOFFICIAL][8.1.0] Dot OS v2.x [BACON [30/03/2018][DISCONTINUED]
[ROM][8.1.0_r33] POSP v1.0 [OFFICIAL]
Nougat (not updating this list anymore)
[OFFICIAL][7.1] LineageOS 14.1 - OnePlus One [bacon]
[ROM][7.1.1_r13] Android Open Source Project | NOF26W [DATE]
[ROM][OPO][7.1.1_r26] Slim7 - Bacon [OMS][NOF27C][Nougat]
[ROM][OPO][7.1.1_r26] Candy7 - Bacon - OOS+Sultan camera [NOF27C][OMS][Nougat]
Android Development
PIE!!!!!
[ROM][9.0.0_R8][PIE] PixysOS [BACON][OFFICIAL]
[OFFICIAL] [AOSP] [WEEKLY] Arrow OS [Pie] [9.0.0_r8] | Bacon [2018-09-22]
[ROM][LineageOS][Android 9.0.0r6]] TugaPower™ 0.6 Beta
[ROM][9.0.0][UNOFFICIAL][Alpha] LineageOS 16.0 for Oneplus One [bacon]
Oreo
[ROM][8.1.0_r4][OMS] LineageOS-15.1 [bacon][BETA][UNOFFICIAL]
[ROM][BACON]RESURRECTION REMIX 6.0[OFFICIAL]
[ROM][LineageOS][Android 8.1.0r36][OMS] TugaPower™ 23.0
[ROM][8.1.0_r36][OFFICIAL] AospExtended ROM V5.7 [DUI]
[ROM][BACON][8.1][OMS] hyperUnicorns - Optimized Dirty Unicorns (discontinued?)
[ROM][8.0.0_r17] halogenOS 8.0 OREO [Testing] [UNOFFICIAL] (unavailable for now)
Dirty Unicorns 12.2 (20180513) (download only). No XDA support! Contact @deadlyindian for a Telegram invitation.
Crdroid ROM for OnePlus ONE crdroid-4.6 (TOP PICK!)
[8.1.x][WEEKLIES] CarbonROM | cr-6.1 [bacon]
[ROM][8.1.0_r42] AOSiP 8.1 [OPO][OFFICIAL]
Validus (shared by @pratikone1 here, have yet to check this) (newer version, still have to check it )
[ROM][8.1.0][OFFICIAL] Cosmic-OS v3.1 - Universe[BACON]
[ROM][8.1.0][UNOFFICIAL] BootleggersROM 3.0-STABLE [BACON]
Nougat (not updating this list anymore)
LineageOS[OMS][DATE][Make CM great again!][Optimized]
[ROM][OFFICIAL][7.1.1_r9][BACON][OPTIMIZED]RESURRECTION REMIX [5.8.0]
[7.1.1] [ROM] Android Ice Cold Project [Official Nightlies] [OMS]
[ROM][7.1.1][OFFICIAL]Android Open Kang Project[AOKP][NIGHTLIES][OMS7]
[DATE][OFFICIAL] 7.1.1 || Ground Zero ROMs || Validus - Tesla - Tipsy
[ROM][OFFICIAL][7.1.1_r6]CypherOS 3.5.1 Jamocha[Bacon]
[OFFICIAL][7.1.1_r9][BACON] XenonHD 7.1[OPTIMIZED][OMS]
[ROM] [7.1.1_r9] [OFFICIAL] [OTA] XOSP - Xperia Open Source Project 7.2
[ROM][OFFICIAL][7.1.1_r4] Zephyr-OS V6.2 [AOSP/Substratum/DUI]
[ROM][7.1][NOUGAT][NIGHTLY] Official Mokee Open Source Project
[ROM][7.1.1_r9][OFFICIAL] AospExtended ROM V3.1 [OMS/DUI]
[ROM][Bacon][7.1][OFFICIAL] Cosmic OS for OnePlus One
[DATE] Unofficial LineageOS 14.1 [OMS7][OPTIMIZED][PERFORMANCE]
[ROM] [bacon] [7.1.1] [LOS-based] **crDroid**v2.0
[ROM][7.1.1_r13] AOSPlusone 7.1 [SultanXDA's Camera HAL][OMS] | 22
Nitrogen OS ► [7.1.1 ► NMF26O] [OMS7] [DATE]
[ROM] [UNOFFICIAL] FLIVERCOD'S CUSTOM AICP-12.1 Android 7.1 [NOUGAT - Bacon] [Linaro]
[ROM/KERNEL][UberTC4.9/Linaro4.9] NucleaRom[Android 7.1.1_r6
[ROM][LineageOS-14.1][7.1.1_r9][OMS7] LegendROM
[ROM][Android 7.1.1]Unofficial Okeys Builds[LineageOS 14.1][OMS7]
[NIGHTLIES] idprophecy's unofficial optimized LineageOS 14.1 builds
[ROM][LineageOS][Android 7.1.1][OMS7] TugaPower 15.1
[ROM] [7.1.1] DarkobasROM [OMNI-ROM]
[ROM][7.1.2][UNOFFICIAL] AIM ROM v2.5 [OMS/DUI][Bacon]
[OFFICIAL][NOUGAT]dotOS-v1.0[Bacon] (this is probably the best one...)
CAF
[ROM][CAF][DATE] halogenOS 7.0 for OnePlus One
Kernel Index
Thunder (Oreo), click here!
FrancoKernel (N + Oreo), click here!
ab123321 Kernel, click here!
Boeffla official, click here!
Boeffla unofficial, click here!
Lightning, click here!
[Changelog]
2018-08-23
Howdy! I've been away (or at least very inactive) for a few weeks due to family vacation and other stuff – including two quite tragic events. That's life I guess
Anyway, interesting development seems to be never ending for this amazing device. The immortality of Bacon has yet again been confirmed with the release of PIE! This was predicted by my teenage antiheroes "Weebl and Bob" back in 2002; they are true visionaries :')
That's not one (KitKat), not two (Lollipop), not three (Marshmallow), not four (Nougat), not five (Oreo) but SIX (PIE!) major Android iterations that have seen light on this chunck of awesomeness. At this rate we might even see Android Queijadinha on the OPO! But let's not get ahead of ourselves. Let's celebrate and enjoy Pie's release first. Time to take a P (Captain Underpants, anyone?). Tra-la-laaa!
Created "PIE!!!!!" section
Added POSP to both Oreo and Pie sections
Added PixysOS
Updated Oreo titles.
2018-05-25
Added Cosmic-OS
Updated all ROM Index Oreo titles
The legendary AOSP by the equally legendary @Agent_fabulous is being discontinued more to come, though?...
Disclaimer: while you are reading this thread, I am shamelessly collecting your personal data. Including but not limited to your shoe size, favourite colour, romantic preferences, how many times you've shouted my username, your failure to use search properly (yes, again!), social security number, blood type, flash habits, flash hobbits (for "precious" ROMs), cookies (both edible and non-edible), the way you're hovering this text with a cursor, etc. You have no right to view, alter or delete this data in any way, I will gain massive profits from it and there's nothing you can do about it. (...) Of course I'm kidding! #GDPRday -_-
2018-04-01
Added CrDroid ¯\_(ツ)_/¯
Added [8.1.x][WEEKLIES] CarbonROM | cr-6.1 [bacon]
Added [ROM] [UNOFFICIAL][8.1.0] Dot OS v2.1 [OMS] [BACON [30/03/2018]
Updated all ROM Index Oreo titles
Free Bacon pr0n: click here (warning: explicit content!)
Happy Easter everyone! ?
2018-03-29
Added RR Oreo added to the ROM Index! LoL, I was so occupied with that ROM today I totally forgot to add it to this list
2018-03-18
Added DU v12.0 Oreo unofficial to the ROM Index because it's just so awesome (and because dev allowed me, lol). There's no XDA thread so don't expect any support. So just.. eh.. #staydirty I guess ^_^
Check out my new animated sig! Created it myself in Photoshop. Let me tell ya, it was a long night
2018-03-15
Added thread jumper on top of OP for people who really hate scrolling :silly:
Oh and a late happy bday, little thread of mine!
older
2018-02-28
Updated Oreo ROM list @ post 2
Moved Franco Kernel up in kernel list (now Oreo compatible) @ post 3
Added CM13 snapshot step in flashing procedure (3.b.)
Updated prerequisites (2.b.) to complement flashing procedure
Added more elaborate info and resources on firmware flashing (2.c.)
Updated all TWRP links to direct download for 3.1.1-5-TugaPower (last stable release of my preferred recovery)
Fixed 'how to check MD5 hash link (was censored?)
Updated file info in 4.c. as audio_platform_info.xml moved to /system/vendor/etc in Oreo
Updated To Do list below
Getting pretty 'ultimate' looking back on first release below, nearly one year since I launched this
2017-12-4
Added 4.e. Can't read or write to internal storage (/sdcard)
Removed changelog bits in OP
Added changelog reference and new/updated legend in index
2017-11-21
Added '1.c. Creating a logcat'
2017-11-15
Reworked the disclaimer
Changed 1.a. stat: from 50,000 to 80,000 installs!
Added Frankenstein Release to firmware (using it myself, quite happy with it)
Replaced "can't find the current release of a ROM" with "EXT4 vs. F2FS"
Updated TWRP links to thread instead of direct download
Made a reference to post #3 instead of listing kernels again
Added link for SDK Platform Tools
Removed optional LOS flash suggestion (obsolete)
Reworked flashing procedure (kernel doesn't need in-between reboot anymore)
Added Magisk reference as root solution
2017-11-12
Updated ROM and Kernel section for Oreo (and Mr.Ak, naturally)
2017-06-27
Added kernel index (post3)
2017-04-07
Bug Fixes and Improvements, lol.
Added '3.a. Installing TWRP' and updated '7.a. ViPER4Android' (to Magisk standard)
2017-03-12
Post #2 is now a Nougat ROM index!
2017-03-12
Added '5.c. QS toggle 'drops' when trying to add it' + video
2017-03-05
First release, not very "ultimate" YET
[To Do]
Elaborate more on kernels (kinda given up on this as Oreo doesn't offer the same freedom we once had in Nougat)
Meh, you tell me!
@Timmmmaaahh
Thanks mate for your helping nature...
I don't know anybody feel or not but you're one of the most helping people of XDA at least for me. I have GOOD memory of your help when my BACON has died and then you helped me a lot, Many people helped me but your help I can't forget...
Thanks mate keep it up..[emoji120]
Unbeatable!
This is going to be fun.
Thanks! @Timmmmaaahh
Edit:
Add Q. What is the codename of Oneplus One?
A. Bacon.
Q. How is this device in over all usage and stuff?
A. Two Word- Bacon FTW!
For those who want TL;DR
There you go
Many thanks for your time
You are our tech Angel
Enviado desde mi A0001 mediante Tapatalk
nachomagic said:
Many thanks for your time
You are our tech Angel
Enviado desde mi A0001 mediante Tapatalk
Click to expand...
Click to collapse
Angel? Lol.
Added 5.c. QS toggle 'drops' when trying to add it + video
[Post#3333] for RR is now the official FAQ.
Nougat ROM INDEX now live!
2017-04-07
Bug Fixes and Improvements, lol.
Added '3.a. Installing TWRP' and updated '7.a. ViPER4Android' (to Magisk standard)
I am planning on a clean flash soon and often refer to your guide as the best source. After all it is titled "The Ultimate OnePlus Guide", so it must be true.
May I request that you begin updating posts #1-#4 to include Oreo? I find the tips you posted here (link) helpful.
cfedata said:
I am planning on a clean flash soon and often refer to your guide as the best source. After all it is titled "The Ultimate OnePlus Guide", so it must be true.
May I request that you begin updating posts #1-#4 to include Oreo? I find the tips you posted here (link) helpful.
Click to expand...
Click to collapse
I honestly thought no one paid any attention to this, lol. Sure thing, I'll try to work on an update this weekend!
How much fat there is in 1kg of bacon?
Timmmmaaahh said:
I honestly thought no one paid any attention to this, lol. Sure thing, I'll try to work on an update this weekend!
Click to expand...
Click to collapse
Don't forget to add roms compiled by me,though.Kthnxbye.
---------- Post added at 12:57 AM ---------- Previous post was at 12:56 AM ----------
Fatsodonkey said:
How much fat there is in 1kg of bacon?
Click to expand...
Click to collapse
The same amount of fat as in 1kg of v0lte.
4.b. My device just exploded!
It's most likely unrelated to a software problem but please, feel free to share pictures!
This made me laugh! :good:
2017-11-12
Updated ROM and Kernel section for Oreo (and @Mr.Ak, naturally)
Mr.Ak said:
Don't forget to add roms compiled by me,though.Kthnxbye.
Click to expand...
Click to collapse
romS? as in plural?
Did I miss any Oreo releases? I'm sure I did...
I'll refresh the OP later, more procrastination first!
Timmmmaaahh said:
romS? as in plural?
I'll refresh the OP later, more procrastination first!
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/development/rom-aim-rom-v2-5-t3693630
I can see you're not as active as before sur.You need to get some v0lte in your life.
Initial post for Sailfish Os for the Samsung Galaxy S2 (i9100) device.
Code:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! W A R N I N G !!
!! !!
!!(Although I am using this on my backup phone)!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! Everything you do, !!
!! you do at your own peril and risk. !!
!! !!
!! I do not bear any responsibility !!
!! for your faulty devices. !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! !!
!! ROM IS NOT SUITABLE FOR DAILY DRIVE !!
!! ONLY FOR EXPERIMENTAL PURPOSES !!
!! !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Making this port was challenging because Sailfish OS, from version 3, doesn't support kernel version 3.0 which is apparently the kernel on the S2.
Fortunately, the SailfishOS-porter guys do very seriously know their business and they are extremely helpful.
From here I would like to emphasize my gratitude towards them for helping me in this project! Thank you!
Requirements:
Before you start to download anything, please read it carefully.
The first requirement is your device must be rooted and you should be able to install a custom recovery (preferably TWRP) onto it.
For this ROM you can either use the stock partitions or you can re-partition to give more space to /system and /data. It doesn't matter which one you chose, I tried and both worked well.
Or if you scroll down to the New partition layout, you can use a completely unique partition layout which gives the most of the internal storage to Sailfish OS. (I currently use my device with this setup.)
Installation instructions:
1. Download all files, CM12.1 zip, Sailfish OS zip, twrp2.8.7.img and kernel*.img to the external SD card on the phone
2. Reboot into TWRP (hold buttons: Power on + Home + Volume up)
3. Do a factory reset
At this point if you want you can repartition the S2 internal storage. (Later you can put the stock layout back if you want to go back to Android.)
The steps for repartitioning are:
Download the 'Repartition: System=1GB, Data=14GB, eMMC=8MB, /preload=7MB' or the 'Repartition: System=1GB, Data=4GB, eMMC=7GB, /preload=0.5GB' .zip file and put into the external SD card. (The difference between these two is explained down at the New partition layout section
Then boot into TWRP and flash the zip as any other zip file. The script first will warn you that it cannot do the partitioning with mounted partitions and it also copies the script itself into /tmp. You just simply need to flash the copied version from /tmp and that will do the trick. The script will format the new partitions accordingly, so once it is completed you can go ahead with the next step.
4. Still in recovery, flash the CM12.1 image
5. Still in recovery, flash Sailfish Os image
6. Still in recovery, flash twrp2.8.7.img to recovery partition
7. Still in recovery, flash kernel*.img to boot partition (this step is not required since sfos 4.4, kernel is installed by flashing the zip file)
8. Reboot
9. Enjoy the latest (4.4.0.68) Sailfish OS on your i9100.
You will need patience as the first boot will take for a while. Then you can go through the initial Sailfish OS set up.
This Sailfish OS Android HAL based on CM 12.1.
Downloads:
kernel12_mtp.img for Sailfish OS 3.2.1.20
kernel33016.img for Sailfish OS 3.3.0.16
kernel34024.img for Sailfish OS 3.4.0.24
kernel41024.img for Sailfish OS 4.1.0.24
kernel43015.img for Sailfish OS 4.3.0.15
twrp2.8.7.img for i9100
CM 12.1 for i9100
Sailfish OS 3.2.1.20 for i9100
Sailfish OS 3.3.0.16 for i9100
Sailfish OS 3.4.0.24 for i9100
Sailfish OS 4.1.0.24 for i9100
Sailfish OS 4.3.0.15 for i9100
Sailfish OS 4.4.0.64 for i9100
Sailfish OS 4.4.0.68 for i9100
Sailfish OS 4.4.0.72 for i9100
Odin v1.83
AOSP-LP-Kernel+_25-08-2015_TWRP-2.8.7.0.tar
Repartition: System=1GB, Data=14GB, eMMC=8MB, /preload=7MB
Repartition: System=1GB, Data=4GB, eMMC=7GB, /preload=0.5GB
Stock partition pit file
kernel07_flatpak (kernel with Flatpak support. Flatpak install/usage instructions.)
Some useful tips:
Low power mode aka ambient mode (in Fingerterm):
Code:
mcetool --set-low-power-mode=enabled
Disable lock screen animation (in Fingerterm):
Code:
mcetool --set-lockscreen-animation=disabled
Some useful patches:
Patchmanager 3.0
More folder icons
Operator name at bottom (Stopped working on 3.3.0.16)
Silica mail (transparent background) - Well documented here
Apps from Openrepos
Apart from the Jolla store there are plenty of other, community-made apps in Openrepos. There is a user-friendly app to install/remove apps from this source called Storeman. It can be downloaded and install from this location: Storeman
Debug/login/troubleshooting:
In Ubuntu, connect USB cable. telnet 192.168.2.15 2323 or SSH [email protected].
Notes:
On Sailfish OS, as it is a Linux system, you cannot install/run any android apps.
How to make a backup/restore with TWRP:
Now the old clunky method is no longer needed. Once you flashed the twrp2.8.7.img to the recovery partition you can boot into TWRP with the usual button combination (Hold buttons: Power on + Home + Volume up) and can make backup/restore.
Instructions for Bluetooth (On Sfos 4.3, BT works normally, don't need this magic)
BT works however turning it on/off is not as user friendly as I hoped. Here is a little instruction/troubleshooting.
Turn BT on (It only works from Settings/Bluetooth!!!!! DON'T try from TOP MENU!!):
If BT hasn't turned on since last boot:
go to Settings/Bluetooth
tap on the dot next to the Bluetooth option
If BT has turned on at least once since last boot:
go to Settings/Bluetooth and tap on the dot next to the Bluetooth option
go back to Settings
go to into Settings/Bluetooth again
tap on the dot next to the Bluetooth option (if it is not turned on repeat from Step 2! Eventually, BT should turn on.)
Turning BT off: Go to Settings/Bluetooth and tap on the white dot next to the Bluetooth option.
Notice: Never try to tap on the white dot twice without going back to the main menu of Settings.
Never try to turn BT on from Top Menu.
However, if you accidentally did any of these BT cannot be turned on again unless you:
reboot the device (this is the easiest) or
in a command line as root issue the following command 'systemctl restart bluetooth-rfkill-event.service' (this will restart the bluetooth-rfkill-event service)
I am not sure how pairing works with different devices.
New partition layout
I mentioned that I tried this Sailfish OS installation with the stock partitions and with another what created for Android 7.1.2. With the stock partitions however was a bit more sluggish than the other one. No wonder as in the stock partitions the /system has only 0.5GB and the /data has only 2GB storage and the rest 12GB is the separate internal storage (eMMC). In Sailfish the entire os (rootfs) including all directories (like /home) live on the /data partition so the 2GB was a bit tight. (The OS itself consumes about 1GB so not much left for apps and other stuff.)
With the other partition layout, the picture was a bit better as the /system had 1GB, the /data got 4GB and the rest 9GB remained for the internal storage. But the partition where the OS lives was separated from the 9GB partition. When I installed a few apps and copied some big files into the /home, I felt the limitation very soon.
Although this layout was sufficient for android but not good enough for Sailfish.
Therefore I have created my own partition table where I restructured the sizes accordingly to my need. (The lanchon repit zip file is available in the download section.)
In this new layout I gave 1GB for the /system (the prior 0.5GB was also fine as the CM12.1 base consumed only 400MB which let a 100MB free space, but I thought that might be not enough in the future so I have chosen 1GB here), I gave only 8MB for the internal storage (eMMC which is mounted into /android directory in this rom), and this made me possible to gave all the rest 14GB to the /data partition. So basically the Sailfish apps and /home can utilize the entire internal storage.
As an extra, on the S2 there is a 0.5GB /preload partition which is hidden and unused by default. In my partition setup I set 7MB to this and the rest almost 0.5GB is also added to the /data.
Go back to stock partitions
In case you would like to do this, you can download the stock partition pit file from the download section.
For this use Odin v1.83 which is also in the download section.
The steps are:
Boot the device into download mode and connect to the PC.
Open Odin v1.83 and tick the 'Re-partition' checkbox at the Option.
Then click on the PIT button and select the downloaded stock pit file.
Then click on the PDA button and select the downloaded TWRP (AOSP kernel) file.
Then click on start.
Done. You need to boot into TWRP and wipe all partitions (system, data, emmc) then you can install the stock rom back. (or if you select the stock rom at PDA instead of the AOSP kernel, it will do the repartition and install the stock rom as well. In this case, you don't need to wipe anything and the device will reboot into the stock Android at the end.)
Changelog:
15.02.2022
=========
General advice:
Patience! All (except camera) apps do start and work but they do need time. This is true for websites. When you clicked on something, wait patiently, eventually, it will start/load.
Work:
Same as previously
Improvement: Stock browser stable and works!
Do not work:
The camera app crashes the device into reboot.
03.09.2021
=========
Work:
Same as previously
Bluetooth does work, but once it is off, needs to be toggled a few times in Settings to make it turn on again.
14.06.2020
=========
Work:
Same as previously + Mobile data is fixed! (To make it work: change Protocol to IP in Settings/Mobile network/Data access point.)
Bluetooth doesn't work, it is still WIP
Do not work:
Same as previously
06.05.2020
=========
The latest version of Sailfish OS 3.3.0.16 is available to download. This requires a different kernel. Both of these can be found in the download section.
Note: With the new version the patch that displays the provider logo at the bottom on the lock screen stopped working. This issue is not related to the OS. The owner of the app should fix it.
Update: In openrepos Kodi is fixed for SFOS 3.3.0.16!
29.04.2020
=========
Work:
Screen
Touch
IMEI number is detected
Sensors (GPS, Rotation, Acceleration, Gyroscope, Magnetometer, Light & Proximity)
Wifi
MTP
Bluetooth (instruction is above)
Calls incoming/outgoing
Messages incoming/outgoing
External SD card detected and mounted to /run/media/nemo/_sdcard_name_ (where _sdcard_name_ is name of the sd card when it was formatted like 7C97-785B)
Internal SD card is mounted to /android
Pixel ratio and icons set to 1.00 (Can be changed to 0.82 which is more appropriate for the device's screen. to do this as root run the 'kimmoli-diyicons.sh 0.82' command. It will fail to install imagemagick but will set the ratio to 0.82 and as we have all icons in place it will work.)
Audio is routed to headphone if that presents
Camera front/rear (only for taking pictures)
Jolla store
findutils is installed by default (updatedb and locate commands work out of the box)
Torch
the charging icon does work properly, however, there is a little delay
can boot into TWRP recovery with the usual button combination (hold buttons: Power on + Home + Volume up)
kernel and recovery .img can be flashed from TWRP (no need for PC to flash Sailfish OS, kernel and recovery)
Low Power Mode (AKA "sneak peek" or "ambient display") works (install instruction is in this post)
The softkeys (each side of the home button) work as notification leds
Do not work:
Mobile data (WIP)
Video recording (It doesn't really work in other 3.x versions either. See my test results here.)
There is an extra little issue that is a delay in screen refresh which is related to how vsync is handled in v10 backend in qt5-qpa-hwcomposer-plugin. I managed to improve this but there is a little delay still. Probably this is the reason why we need to jump back to Settings every time before trying to turn BT on, but I am not sure.
04.04.2020
=========
Work:
Same as previously + Softkeys are used as notification leds
Bluetooth doesn't work, it is still WIP
Do not work:
Same as previously
23.03.2020
=========
Work:
Same as previously + with 'kernel12_mtp' the MTP works!
Bluetooth partially works (to switch on BT requires a reboot or issue a command manually, it is still WIP)
Do not work:
Same as previously
25.02.2020
=========
Work:
Same as previously + with 'kernel07_flatpak' the Low Power Mode (AKA "sneak peek" or "ambient display") works! (install instruction is in this post)
Do not work:
Same as previously
23.02.2020
=========
Work:
Same as previously + but from now on you don't need PC and heimdall to flash kernel and twrp
Do not work:
Same as previously
19.02.2020
=========
Work:
The same as listed earlier + with the new kernel (kernel06) I attached you can boot into TWRP with the usual button combination (hold buttons: Power on + Home + Volume up)
Do not work:
Same as previously except the TWRP/Sailfish OS boot which has fixed.
08.02.2020
=========
Work:
Screen
Touch
IMEI number is detected
Sensors (GPS, Rotation, Acceleration, Gyroscope, Magnetometer, Light & Proximity)
Wifi
Calls incoming/outgoing
Messages incoming/outgoing
External SD card detected and mounted to /run/media/nemo/_sdcard_name_
(where _sdcard_name_ is the name of the sd card when it was formatted like 7C97-785B)
Internal SD card is mounted to /android
Pixel ratio and icons set to 1.00 (can be changed, I set 0.82 which is more appropriate for the device's screen resolution see the download section)
Audio is routed to headphone if that presents
Camera front/rear (only for taking pictures)
Jolla store
findutils is installed by default (updatedb and locate commands work out of the box)
Torch
Do not work:
Mobile data
Bluetooth (the bt driver is in the kernel, so in theory, with some config file changes on the device it can work)
MTP
Video recording (It doesn't really work in other devices with CM12.1 base.)
Screen delay in refresh (related to how vsync is handled in v10 backend in qt5-qpa-hwcomposer-plugin)
the charging icon doesn't work properly: when the device is not on charger still shows it's charging (when I unplug the cable the message appears: "Charging..."
cannot boot into TWRP recovery (See Notes above)
Battery life:
In my experience the battery life is good. On standby, it can survive 10 days. (Almost 11.) I have checked once or twice daily during this period.
{
"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"
}
Pictures:
App drawer
Top menu
Settings
About product
In case somebody missed these I would like to highlight some improvements since day 1:
Now both the kernel and twrp can be flashed as an .img from twrp (no need for PC and heimdall anymore)
Plus I uploaded a kernel with Flatpak support
With kernel07_flatpak, I have installed Flatpak and Angelfish but got an error when started Angelfish.
It looks like this is a limitation of the old kernel, but there might be a workaround.
I'll keep you posted.
With kernel12_mtp, MTP works. (and bluetooth partially)
The soft keys each side of the home button are used as notification leds. As this device doesn't have leds, the softkeys can be re-used as "leds". They do blink if the device is fully charged or there is an unread incoming text message. When the device is on charger they are on, otherwise both of them are off.
Can you post your sources? I'm interested in getting an I9100 as my new phone, and was considering a port and I'm happy to see you've already done all the leg work and then some!
Also about the kernel on this phone, I've been trying to port to a tablet with weird kernel images, can you run "file (path to android base kernel image)" - if it says ForPro FPT or similar I will be very very interested in how you got this phone to boot into rootfs. Very interested in the progress you've made though :3 Thanks for the awesome rom!
Galaxyninja66 said:
Can you post your sources? I'm interested in getting an I9100 as my new phone, and was considering a port and I'm happy to see you've already done all the leg work and then some!
Also about the kernel on this phone, I've been trying to port to a tablet with weird kernel images, can you run "file (path to android base kernel image)" - if it says ForPro FPT or similar I will be very very interested in how you got this phone to boot into rootfs. Very interested in the progress you've made though :3 Thanks for the awesome rom!
Click to expand...
Click to collapse
Sorry for delay in my reply.
The necessary repos in github are:
local manifest
dhd (in here the dhd submodule has to be refreshed from mer-hybris repo upgrade-3.2.1 branch)
droid-hal-i9100
droid-hal-version-i9100
android_device
kernel
The file (path to android base kernel image) command gives me: "Linux kernel ARM boot executable zImage (little-endian)"
A new image has been generated and can be downloaded. This one includes the patch of reusing the two softkeys (each side of the home button) and they do work as a notification leds!
Currently I am working on the mobile data and bluetooth (this latter partially works but is not reliable yet).
You're a g! I just bought an i9100M (different radio ).
I do recall ofono being unfriendly towards older RIL versions, galaxy nexus afaik is unfixable in 2.0+. However, if you have any service that is exciting! I can't wait to setup my environment and play around with this! If i9100M has a different partition layout/mount points (you know how samsung is) I will blow my brains out. How is camera working? Does this image include gstreamer/droidmedia?
You've probably got this sorted way better than I could hope to sort it! I'm shocked this doesn't have more replies.
EDIT: I noticed you have a complex patch for the pixel ratio. Have you tried just setting it in your patterns?
Galaxyninja66 said:
You're a g! I just bought an i9100M (different radio ).
I do recall ofono being unfriendly towards older RIL versions, galaxy nexus afaik is unfixable in 2.0+. However, if you have any service that is exciting! I can't wait to setup my environment and play around with this! If i9100M has a different partition layout/mount points (you know how samsung is) I will blow my brains out. How is camera working? Does this image include gstreamer/droidmedia?
You've probably got this sorted way better than I could hope to sort it! I'm shocked this doesn't have more replies.
EDIT: I noticed you have a complex patch for the pixel ratio. Have you tried just setting it in your patterns?
Click to expand...
Click to collapse
I am not sure what you d understand under 'any service' but except the mobile data, everything else works fine (calls in/out, texts in/out).
I don't know the difference between the i9100 and i9100m but on the internet you probably can find something about it.
One suggestion, before you start porting, install an android onto and boot into that and note the mounting points. This can save a little time when you need to set the fixup_mountpoints in hybris-boot.
The camera works but only for pictures. The video recording doesn't work. I think this is down to the cm12.1 base what I used for my port. I think gstreamer/droidmedia are there but am not sure.
I think the reason why this doesn't get more hype because this is a very old device and except some old fashioned folks like us, not many are using anymore. I don't mind it because this is my hobby. I am going through a to-do list until all I wanted works.
Currently, as the new version 3.3.0.14 is out) I am working on to update my port to 3.3.0.14. Unfortunately currently there is no OTA but hope eventually it will be sorted.
Changing the pixel ratio is not essential as the default 1.0 is ok-ish. I have found the 0.82 better so I included the icons into my image. As the script (kimmoli-diyicons.sh) is also included, we just need to run one command as root. I may try to set the 0.82 out of the box but currently it is not my to priority. As I will need to re-build everything for 3.3.0.14, I will try to set 0.82 in the pattern file.
Please keep me posted with your progress.
edp17 said:
The camera works but only for pictures. The video recording doesn't work. I think this is down to the cm12.1 base what I used for my port. I think gstreamer/droidmedia are there but am not sure.
Click to expand...
Click to collapse
You'd 100% know if you built gstreamer, it's specified in the middleware section iirc and you have to uncomment it from your patterns. I hope it's easier to build nowadays. Also I noticed your port wasn't on the mer-wiki, if I remember my login is it okay if I add it :3 ?
EDIT: https://wiki.merproject.org/wiki/Adaptations/libhybris#Samsung - I added it to the bottom. creditted you in the edit note. you can create an account on the mer bug wiki and use it to edit the tables. I'll also be closely following this and editting it to match your progress. Tell me if you'd like any values changed!
Galaxyninja66 said:
You'd 100% know if you built gstreamer, it's specified in the middleware section iirc and you have to uncomment it from your patterns. I hope it's easier to build nowadays. Also I noticed your port wasn't on the mer-wiki, if I remember my login is it okay if I add it :3 ?
EDIT: https://wiki.merproject.org/wiki/Adaptations/libhybris#Samsung - I added it to the bottom. creditted you in the edit note. you can create an account on the mer bug wiki and use it to edit the tables. I'll also be closely following this and editting it to match your progress. Tell me if you'd like any values changed!
Click to expand...
Click to collapse
I remember that I built gstreamer and un-commented the related stuff in the pattern file. I don't know whether easier to build now because I don't know how difficult it was before. I only can compare this project against my hammerhead one a few months earlier. For the hammerhead I needed to build the image with MIC, now the rpm/dhd/helpers/build_packages.sh command does everything for you. (For this you need to export the RELEASE, EXTRA_NAME values in your .hadk.env)
Unfortunately I still don't have OBS account so I couldn't add this device into the wiki. Thank you for doing that! Unfortunately new account creation on the mer bug wiki is restricted at the moment.
I have checked the wiki you have added and if you don't mind I would like you to amend a few things:
LED works (the two softkeys have repurposed as notification leds)
GPS works
Sensors Gyro and Magnetometer both work
(I need to double check the RTC alarm and USB net.)
I updated the page. I was going to set up my build env but seeing your row in the adaptations page made me realise you're so far along, and there isn't anything I could really do to push things forward by much. Once you get data and camera working this is pretty much one of 2 daily driver stable samsung sfos ports. Congrats :3 !
Galaxyninja66 said:
I updated the page. I was going to set up my build env but seeing your row in the adaptations page made me realise you're so far along, and there isn't anything I could really do to push things forward by much. Once you get data and camera working this is pretty much one of 2 daily driver stable samsung sfos ports. Congrats :3 !
Click to expand...
Click to collapse
Thank you for the update and for the congrats but I think it is only partially my merits. I probably couldn't done this without the help of sailfishos-porter guys.
As I mentioned in the main comment, I am using my S2 with this image on it as a secondary phone already. Mobile data is not crucial as my main phone can be a hotspot and with my S2 I can connect to it via wifi. Of course this doesn't stop me trying to make that work. (The BT was almost done but I then broke something.)
The camera is a different story. Afaik the video recording generally is broken in the CM12.1 base that I chosen for this device. (That doesn't work on my hammerhead which is also using CM12.1 base.) So I think that will remain outstanding unless I try to port with a different android base.
I think will stop with this for while because the new version (3.3) is out soon and would like to upgrade to it first, then continue working on the missing bits.
Video recording works in the latest scm12.1 snapshot (YOG7D). I wish they hadn't tanked the old etherpad faq, I swear I saw something about hybris 12.1 specific video recording stuff.
If I can find another sub 20 USD i9100 I am definitely working on this, but since my i9100m is my daily driver and dualbooting isn't as easy as with other devices (espescially since YOG7D doesn't have isorec committed ). Thanks for getting so much done though, You have no idea how much it means to me that Sailfish OS is available for our device, and so stable too! :laugh:
Galaxyninja66 said:
Video recording works in the latest scm12.1 snapshot (YOG7D). I wish they hadn't tanked the old etherpad faq, I swear I saw something about hybris 12.1 specific video recording stuff.
If I can find another sub 20 USD i9100 I am definitely working on this, but since my i9100m is my daily driver and dualbooting isn't as easy as with other devices (espescially since YOG7D doesn't have isorec committed ). Thanks for getting so much done though, You have no idea how much it means to me that Sailfish OS is available for our device, and so stable too! :laugh:
Click to expand...
Click to collapse
I think the video recording also works in cm12.1 on the android side, but the problem is a, between the android and Sailfish or b, on the Sailfish side. I am not sure but when I tried to fix it on the hammerhead (same cm12.1 base) I was told the recording was broken in general with cm12.1 base. I'll see how it works (what I can do about it) after Sailfish 3.3 is out.
Have you thought about to purchase a cheap android phone to use as daily driver and using the i9100m for your Sailfish project? (You probably can get a decent second hand android phone for sub 20 maybe with better spec than the i900.)
Thanks again for the kind words. This phone (the S2) is my favorite old friend. It is indestructible . I have soft bricked so many times and managed to install many other OS but as couldn't find Sailfish OS, so I though worth a try to port. And with support of the Sailfishos-porters guys, my dream became real :good: .
Sailfish
Wow, great. I installed and the system works! Bluetooth does not work after installing the packages, but bluetooth-rfkill-event- * are not installed (error). There are few programs in the system, however. Especially browsers, the standard one hangs up (maybe there is a third-party?). Slightly slows down, but bearable.
By the way, are you not working with @linusdan? It also seems to be working on the port github com /sailfish-i9100 (link)
Sorry no link rights.
P/s By the way, I saw on the postmarket wiki site for i9100 about working kernels for our device. Available: kernel version 4.2 or mainline kernel
S2UserRU said:
Wow, great. I installed and the system works! Bluetooth does not work after installing the packages, but bluetooth-rfkill-event- * are not installed (error). There are few programs in the system, however. Especially browsers, the standard one hangs up (maybe there is a third-party?). Slightly slows down, but bearable.
By the way, are you not working with @linusdan? It also seems to be working on the port github com /sailfish-i9100 (link)
Sorry no link rights.
P/s By the way, I saw on the postmarket wiki site for i9100 about working kernels for our device. Available: kernel version 4.2 or mainline kernel
Click to expand...
Click to collapse
I am glad you managed to install it. Have you tried to re-partition the internal memory as I advised?
Yeah, the bt and mobile data is still WIP status. Hopefully will have some time to complete them soon.
For the browser, the native one doesn't hang for me. You can try to look for and install one from the openrepos. (I suggest to install the Storeman as you will find more useful apps for Sailfish OS.)
I don't know linusdan but have seen he has checked this post already. Hope he also found it useful.
I am aware of the postmarketos for the S2 and tested it on my S2. At that time (about a year ago) there was no mainline linux kernel option for the S2. Unfortunately the mainline kernel doesn't help with Sailfish because the Samsung proprietary blobs are missing from there. This means Sailfish wouldn't work. It needs the drivers from the Android layer.
S2UserRU said:
Wow, great. I installed and the system works! Bluetooth does not work after installing the packages, but bluetooth-rfkill-event- * are not installed (error). There are few programs in the system, however. Especially browsers, the standard one hangs up (maybe there is a third-party?). Slightly slows down, but bearable.
By the way, are you not working with @linusdan? It also seems to be working on the port github com /sailfish-i9100 (link)
Sorry no link rights.
P/s By the way, I saw on the postmarket wiki site for i9100 about working kernels for our device. Available: kernel version 4.2 or mainline kernel
Click to expand...
Click to collapse
I forgot to mention that there should be a folder '/edp17packages/bluetooth' where you can find the missing packages for the bt. Once you installed it, probably only need to tweak some config files and need to create some scripts. I currently started working on it.