LinuxForExynos Group PresentsA WONDERFUL NON WORKING LINUX DISTRO THAT DOESNT EVEN TRY TO BOOTANYWAYS TO FLASH IT:First, flash TWRP or OrangeFoxSecondly, flash Astrako's Partitioner Script from here https://forum.xda-developers.com/t/...epartition-script-for-vendor-support.4143541/ . What this does is it makes your system partition to 4GB, which is good for PostMarketOS. Flash this and reboot to recovery. WARNING: ALL DATA WILL BE GONEThirdly, download PostMarketOS from the links given below and flash it via PBRP. it is automatic and please do NOT opt in for Full Disk Encryption as it will break the phone.Fourth, reboot and enjoy! For now this only has a terminal with a touch keyboard. The login is `user` with the password `12345`.If it works for you or doesn't PLEASE let me know and please do note that this is alpha build software and you should not use it as a daily driver or expect your phone to be stable. Thank you.
Contributors:
@Astrako for his repartition script
@Parthib and DedSec#3307 for their VPS
@zpunout and @thinhhdk for their time and effort and testing the product
@thinhhdk for patches
AFH and GitHub for letting me host the files
Download V1.1:
pmos-on7xelte-31JAN.zip | by Otus9051 for Galaxy J7 Prime
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Release Boots initramfs, no networking yet, includes LXDE. · LinuxForExynos/pmos-samsung-on7xelte
This build now has a booting initramfs and working usb. Networking and display and other stuff isnt working.
github.com
Download V1:
pmos-samsung-on7xelte.zip | by Otus9051 for Galaxy J7 Prime
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
https://files.catbox.moe/fxphum.zip
pmos-samsung-on7xelte.zip
drive.google.com
I am working on a pmOS port to G610F. Currently there is a port for the J710F (https://wiki.postmarketos.org/wiki/Samsung_Galaxy_J7_(2016)). This new port will be based on that. Due to me breaking my grandma's phone, she actually has the G610F, also yes she is outstation so I don't have the phone, so, basically I need testers for the new port. Every single development enhancements, milestones and builds will be provided here. As of now, I have the source at https://github.com/LinuxForExynos/pmos-samsung-on7xelte. If you have any suggestions or are interesting in developing or testing, please reply to this thread or hit me a dm at Otus9051#5971 in discord. This project won't be possible without you. Also, I am developing Halium for it too, so this thread will also have this too.
Requirements for testing:
Knowledge with Linux (atleast upto knowing how to cd or cp, the more the better)
Time (a lot)
My PBRP build (https://forum.xda-developers.com/t/...-pitch-black-recovery-project-v3-1-0.4287985/) [actually any twrp build but this one has a better terminal ui and looks cool]
A G610F, with my pbrp
Requirements for development:
why am i putting this but anyways
Knowledge with Alpine Linux and Linux Kernels
Knowledge with DTBs and stuff and android ofc
A laptop/pc with Linux (not wsl) and atleast 6gb ram and a dual core processor
-------------
Otus9051 said:
MODS PLEASE SEE THIS!!!
Click to expand...
Click to collapse
My apologies for my earlier mistake. Carry on my friend.
Cheers: Badger50
Badger50 said:
My apologies for my earlier mistake. Carry on my friend.
Cheers: Badger50
Click to expand...
Click to collapse
It's ok man
I have here a G610Y. My knowledge of Linux (Debian/Ubuntu/Mint) I think is somewhere between beginner and intermediate. I am familiar with flashing to partitions on the phone with Heimdall though.
zpunout said:
I have here a G610Y. My knowledge of Linux (Debian/Ubuntu/Mint) I think is somewhere between beginner and intermediate. I am familiar with flashing to partitions on the phone with Heimdall though.
Click to expand...
Click to collapse
I will be releasing the first release of pmOS (probably non-booting) in a couple of weeks. Thanks for your interest and help!
@zpunout new release in a bit, getting the dtbs rn
btw if you have discord or anything hit me a dm with your tag, matrix works too. just dont wanna clutter this thread up
Otus9051 said:
@zpunout new release in a bit, getting the dtbs rn
btw if you have discord or anything hit me a dm with your tag, matrix works too. just dont wanna clutter this thread up
Click to expand...
Click to collapse
Matrix works for me. I just set up an account
zpunout said:
Matrix works for me. I just set up an account @zpunout:matrix.org
Click to expand...
Click to collapse
DMed ye
Ran into a big problem: pmbootstrap is broken
its workin'
@zpunout get ready with latest stock, DO NOT BOOT PLEASE I BEG YOU, and flash my recovery instead of stock recovery at the time of flashing. and do not boot to system.
still compiling
See the Main Post for Links
> (doesn't work lol[if you thought it would well no your dreams are gone])
Can confirm, doesn't boot, stuck at samsung splash screen, charging doesn't show percentage so maybe kernel problems.
Yeah, I and zpunout are working on it. Infact, WE HAVE NO LEADS LOL so uh yeah i have to do some digging i guess... The biggest problem is that I don't have the device itself right now so it makes it a bit difficult to work and apply patches. My current workflow is Patch > Build > Upload > Test > Repeat
And uploading takes a long time where I live like a 200MB file takes 10mins to upload... Yeah...
Otus9051 said:
Yeah, I and zpunout are working on it. Infact, WE HAVE NO LEADS LOL so uh yeah i have to do some digging i guess... The biggest problem is that I don't have the device itself right now so it makes it a bit difficult to work and apply patches. My current workflow is Patch > Build > Upload > Test > Repeat
And uploading takes a long time where I live like a 200MB file takes 10mins to upload... Yeah...
Click to expand...
Click to collapse
I want to be a tester, i sent a friend request on discord
It might seem that development is dead but its not. It takes more than a year to complete each port. Please have patience. You can track our progress at https://github.com/LinuxForExy7870/
failed to mount /system_root
serelafo said:
failed to mount /system_root
Click to expand...
Click to collapse
Its a common problem. It has still installed nonetheless.
FYI, project still alive, working on Android 12 currently.
Related
This thread is intended for developers and others who can contribute to the project
If you think you can contribute, please do so
Standard disclaimer:
I am not responsible if anything happens to your device
Status:
Device specific build of Ubuntu's minimal cm10.1 build ready
Ready for flashing
Working:
Touch screen
ADB
Browser (Although no net access yet)
You can browse and get a feel of the entire OS, including the homescreen (unity desktop), multitasking (the cool new way to switch between apps), etc.
Since it is a preview, many apps are dummy apps.
Screenshots:
Check them out here
Video:
Here is a video of the fresh new OS in action on the O2x made by JordanRulz
Download links:
Ubuntu touch preview (raring ringtail)
Current build of Ubuntu-CM10.1 (old bootloader)
New bootloader build by delaya73:
cm-10.1-20130604-UNOFFICIAL-p990.zip
Older Ubuntu phone quantal image
older build 2 of Ubuntu-CM10.1 by delaya73
older build 1 of Ubuntu-CM10.1 by delaya73 for the new bootloader
TWRP latest version is recommended (CWM 6.x may work too)
Note:
The raring/quantal image is large, but thankfully gets installed on the data partition, thus saving our small system partition the burden
Source:
Ubuntu-cm10 source
Building instructions:
Building instructions are similar to building CM10 (refer Raum's guide) till repo sync (instead of official cm10 repo, use above source during repo init)
Dont forget to add device props in "local_manifests" (local_manifest.xml is deprecated). Add the following in local_manifests:
Code:
(Taken from Raum's guide, thanks to him)
After syncing the repo,
1. cd device/lge/p990, connect your device running cm10.1 with usb debugging on, and then ./extract-files.sh
2. In device/lge/p990/fstab.p990, remove "nosuid" from data partition
3. In kernel/lge/star/arch/arm/configs, in cyanogenmod_p990_defconfig, add the following:
Code:
CONFIG_SYSVIPC=y
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
CONFIG_USER_NS=y
CONFIG_PID_NS=y
CONFIG_NET_NS=y
CONFIG_DEVTMPFS=y
CONFIG_DEVPTS_MULTIPLE_INSTANCES=y
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_FANOTIFY=y
CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y
CONFIG_FSNOTIFY=y
CONFIG_SWAP=y
# CONFIG_ANDROID_PARANOID_NETWORK is not set
4. Go to ubuntu folder inside your source folder and do
Code:
bzr branch lp:phablet-extras/libhybris hybris
bzr branch lp:platform-api platform-api
If you didnt have bzr, get it first using
Code:
sudo apt-get install bzr
Now you can build. This build would be for the old bootloader. For the new one, make these changes said by pengus77 here
Flashing instructions:
1. Make a full wipe (wipe data + format /system)
2. Flash the current build and raring/quantal image
Then flash this afterflash.zip
3. Reboot
Credits:
Ubuntu dev team (Canonical)
Ricardo and the rest of the CM team
delaya73 for the new bootloader build
pengus77 for bringing cm10 to the new bootloader
Adam77Root for helping find the missing components stopping it from booting
All other contributors
AW: [DEV][WIP] Porting Ubuntu Phone for LG Optimus 2x
You rock man!
Gesendet von meinem LGP990 mit CM10.
Good luck with your job, Buddy, and Congratulations for all your interest/performance for our machines!
Regards.:good:
Thnx, I downloading, after a try, I will post some feedback
R: [DEV][WIP] Porting Ubuntu Phone for LG Optimus 2x
Can i have some screenshot?
Sent from my LG-P990 using xda app-developers app
rugglez said:
"...If you think you can contribute, please do so ..."
Click to expand...
Click to collapse
I have not had time to install this ROM ... I have been testing other, but lack little longer to do so!
Once you have news post here the results.
Thank you all for the effort made
Thank you man you're doing a really good job
Very good job rugglez bro. cant wait for bootable version to test it on my self
Well, I tried to make some tests to see if he could complete the boot ... unfortunately without success after six or seven attempts.
Enough for today testing, hahahaha! ...
So finally your Repo synced! I've left Hope here! And yea, Rugglez Bhai, you are great! )
rugglez said:
This thread is intended for developers and others who can contribute to the project
If you think you can contribute, please do so
For now, this is only for the new bootloader. If the project is successful, it would be made available on the old one as well
Standard disclaimer:
I am not responsible if anything happens to your device
Status:
Device specific build of Ubuntu's minimal cm10.1 build ready
Ready for flashing
Does not complete the boot yet
Download links:
Current build of Ubuntu-CM10.1
Ubuntu kernel for O2x
Ubuntu phone quantal image
TWRP latest version is recommended (CWM 6.x may work too)
Instructions:
1. Make a full wipe (wipe data + format /system)
2. Flash the current build, Ubuntu_kernel and quantal image
3. Reboot
Note:
The quantal image is large, but thankfully gets installed on the data partition, thus saving our small system partition the burden
To do:
There is no "logcat" in Ubuntu (may be some other way to debug), so need another way to look at what is preventing the boot
Credits:
Ubuntu dev team (Canonical)
CM team
All other contributors
Click to expand...
Click to collapse
have u tried dmsg/kmsg?
how did u get a bootanimation on there ?, my nexus 7 with ubuntu phone os, dont have one, on the nexus 7 there is only a black screen for a seconds then it boots up
Re: [DEV][WIP] Porting Ubuntu Phone for LG Optimus 2x
Never got around to syncing myself, I'm a bit confused regarding the post, so is it usable?
Sent from my LG-P990 using xda app-developers app
JordanRulz said:
have u tried dmsg/kmsg?
Click to expand...
Click to collapse
Will try that today. Not sure if ill get time, but if you could also have a look, it would be great. Saw that you have some experience with this
FettleifIsMyUserName said:
how did u get a bootanimation on there ?, my nexus 7 with ubuntu phone os, dont have one, on the nexus 7 there is only a black screen for a seconds then it boots up
Click to expand...
Click to collapse
Boot animation comes from the Ubuntu-cm10.1 build and is the default cm10 boot animation. Since your tablet's Ubuntu image was released directly by canonical, they must have removed the cm10 boot animation before releasing it
Neefy said:
Never got around to syncing myself, I'm a bit confused regarding the post, so is it usable?
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
If you read the first post, it's written there that it does not complete the boot yet, still a WIP.
The reason I posted was that if more contributors join in, more expertise, more time, better debugging and much higher chance of project success
Jishnu Sur said:
So finally your Repo synced! I've left Hope here! And yea, Rugglez Bhai, you are great! )
Click to expand...
Click to collapse
Thanks
Come online later, I'll help you fix that issue. Install and keep team viewer ready
After watching some vids about this OS, it trully have a great potential. gonna watch this thread closely for progress
Re: [DEV][WIP] Porting Ubuntu Phone for LG Optimus 2x
rugglez said:
Thanks
Come online later, I'll help you fix that issue. Install and keep team viewer ready
Click to expand...
Click to collapse
Nice to know that the team is joining up and viewing to do great things
Great going guys
O2X with Magical ICS ROM and magnificent kernels from my buddies
rugglez said:
Will try that today. Not sure if ill get time, but if you could also have a look, it would be great. Saw that you have some experience with this
Boot animation comes from the Ubuntu-cm10.1 build and is the default cm10 boot animation. Since your tablet's Ubuntu image was released directly by canonical, they must have removed the cm10 boot animation before releasing it
If you read the first post, it's written there that it does not complete the boot yet, still a WIP.
The reason I posted was that if more contributors join in, more expertise, more time, better debugging and much higher chance of project success
Thanks
Come online later, I'll help you fix that issue. Install and keep team viewer ready
Click to expand...
Click to collapse
M always ready!!!!!!!!! =D
The Credits list looks too small.
Maybe you can add Ricardo Cerqueira (for ahem) and TonyP for porting TWRP.
jasjeev4 said:
The Credits list looks too small.
Maybe you can add Ricardo Cerqueira (for ahem) and TonyP for porting TWRP.
Click to expand...
Click to collapse
......and so on...!...
jasjeev4 said:
The Credits list looks too small.
Maybe you can add Ricardo Cerqueira (for ahem) and TonyP for porting TWRP.
Click to expand...
Click to collapse
Ricardo is always a name in every project of the O2x, and he is a part of the CM team, in case you didnt know
But thanks for the reminder, I explicitly specified his name too now, deserves so much credit for bringing CM10 to our device.
Tonyp is a great contributor and we are thankful for all his work. But this is a ROM, and TWRP is a recovery used to flash a ROM, they have non-overlapping work. What I mean is, this ROM doesnt use TWRP's work, rather it can be flashed in TWRP or CWM6.
By your logic, Koushik Datta (developer of CWM and one of the best android devs) should be included in every ROM's credits here. Also, creators of USB, personal computers, internet, world wide web, which are also tools used in the process of flashing it.
(No offense meant to any of the above, they are all revolutionary people whom I greatly respect)
My point is, if I am using someone's work in this project/ROM, thats the person whose name goes in credits, not the one who is creating the tools to install it.
It's better if the discussion doesnt go further about this off-topic thing, if you find that I have used anyone's work in this ROM and not given credits, please let me know, thanks
Let's try to make Ubuntu Phone OS boot on our phone. Thats the priority here. Didn't get much time today, got college this week too, will see if I get time to work on it soon
I have put this project on hold for now. I flashed latest Austrian ICS build to my device and continue using it as my Kindle reader on my travels. IF somone manages to fix the two issues with kernel, send me a message and I'll continue working with the repository. But for now I'm not thinking nor touching the subject before Easter. Thank you for participating for now
I've started porting Ubuntu-touch dev-preview to the Galaxy Tab 7.7 (3g). If you do not understand it already, you flash this at your own risk. There is now also a Ubuntu-touch specific device page here: https://wiki.ubuntu.com/Touch/Devices/p6800. I'll try to keep this thread and the Ubuntu devices page as close to each other as possible.
Big thanks to Daniel_hk for helping with boot.img Now It can be booted, but the screen is still black
Also, without working wifi and display, the preview is basically unusable... Next steps should be these:
1. Get wifi drivers working.
2. Get display drivers working.
Code:
[email protected]:/# uname -a
Linux localhost 3.0.15-CM-g1dc3074 #2 SMP PREEMPT Wed Mar 13 00:43:37 EET 2013 armv7l armv7l armv7l GNU/Linux
Repositories:
Latest release tagged with: "v0.3", not tested!
https://github.com/dun1982/android_device_samsung_p6800
https://github.com/dun1982/android_kernel_samsung_p6800
Download
cm-10.1-20130312-UNOFFICIAL-p6800.zip
Daily Ubuntu image: http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/
Installation
Install CWM 6.0.2.8
Wipe data/factory reset
Wipe cache partition
Flash cm-10.1-20130312-UNOFFICIAL-p6800.zip to device
Flash quantal-preinstalled-phablet-armhf.zip to device
Reboot
Starting to use
Then it gets interesting (Black sreen for now now Run the following commands in your desktop system:
Code:
adb root
adb shell
ubuntu_chroot shell
You should have now root access inside your tabled. Continue with this wiki next
What works
Ubuntu-touch dev-preview is flashable.
It boots!
Known Issues
Kernel is based to the CyanogenMod/android_kernel_samsung_smdk4210, but it is a mess. So forked it, took code here and there (mostly from locerra's JB build).
Kernel is based 3.0.15 and no newer one available (yet).
Most of the drivers in kernel had to be turned off, because build was not succeeding...
bluetooth: Doesn't work
audio: Dock audio doesn't work.
hwcomposer: HDMI dongle doesn't work.
wifi: Doesn't work.
camera: Doesn't work.
.. and lot of kernel level bugs for sure.
Displaydrivers are not working (yet).
Release notes
Version 0.2 (13.03.2013) - Now it boots, see release notes
Version 0.1 (07.03.2013) - Intial release, nothing works
Credits
BIG THANKS to daniel_hk for solving the boot.img problem for me.
Anyone who has worked previously with the device/kernel source.
locerra (for getting CM10.1 to flashable state).
wowww!!! thank you !test now:victory::victory:
Placeholder for future.
Re: [ROM][P6800]Ubuntu-touch dev preview(02.03.2013)
Not 6810 versión?
AUs
el_campi said:
Not 6810 versión?
AUs
Click to expand...
Click to collapse
I cannot test it for anything else. The kernel sources are from CM10.1 that was in use from locerra, so in theory it should work with i815 and with p6810 as well. But I cannot give you any guarantees...
And also before I get this build to even start with my device, I do not think that sharing image would help anyone. But if you are a developer, I would like to talk with you on issues that I might have missed or done wrong. So contact me
Re: [ROM][P6800]Ubuntu-touch dev preview(02.03.2013)
any update?
Sent from my GT-P6800 using xda premium
Not much. The generated image is missing /data/ubuntu completely and that is the reason why the image does not boot. I got also flu and fewer, so I have had not that much time after the weekend to look on the issues on that.
I'm also waiting if I get any answers from Ubuntu touch emailing list regarding the problem and where to look for answers, but my quess is that it has something to do with the devices fstab file...
Good news everyone!
Just got a very good answer the problem I had with the /data/ubuntu-folder missing from the image. There was no image provided for the actual Ubuntu at all by the build-process...
When I get home from work, I'll try to find time to look into the build process if I can include the actual Ubuntu image to the ready made image and then release it after I get my device to boot. But it seems that I got the right nudge forward for this now :highfive:
Hmpf, still not booting. Now the /data/ubuntu logs are unmodified, which would point towards kernel or fstab-issue (ie. /data/ubuntu is never used...).
Re: [ROM][P6800]Ubuntu-touch dev preview(02.03.2013)
Good job :thumbup::thumbup::thumbup::thumbup::thumbup::thumbup:
Sent from my GT-p6800 using xda premium
Doh... still not working... Any ideas anyone?
Ok, new version build from different repositories (thx, danile_hk for tip).
I'll test the new image this evening when I get back to home, and I have my fingers crossed that I can get the device to boot up and even display something useful. After that I can start looking for ubuntu developemnt
New version did not work, but then Daniel_hk gave me working boot.img. So now I need to find out what the heck is wrong with my repository and fix it so that I can get working boot.img from start and also the device configuration has issues. Both repositories are currently out of sync I'm afraid
dun1982 said:
New version did not work, but then Daniel_hk gave me working boot.img. So now I need to find out what the heck is wrong with my repository and fix it so that I can get working boot.img from start and also the device configuration has issues. Both repositories are currently out of sync I'm afraid
Click to expand...
Click to collapse
Also, without working wifi and display, the preview is basically unusable... Next steps should be these:
1. Get wifi drivers working.
2. Get display drivers working.
It seems that I hit the wall (again) with the mentioned big issues.
For now, I keep some sabbatical from Ubuntu Touch things (ie. I flashed ICS Austria to my device) and use it as my Kindle reader again.
If by miracle I get more info regarding how to get the Kernel working with Ubuntu Touch, then by allmeans I continue working with this project. So far it just seems that making a working image, is out of my hands currently.
At least you had a go. Thanks for your efforts, and hope you might have another crack at it later on.
I'm feeling a little bit that way right now too, and put my ICS kernel on the back burner. I think I'm trying to multitask a little too much at times....
Yep, a break is what you need, maybe some clarity will come after you've had a chance to recharge.
Sent from my GT-I9300 using xda premium
It's very nice to see you took up the big responsibility to make this superb device to be usable again! it has great specs, really. KUDOS bro!!
Any update on this development?
ZhenMing said:
Any update on this development?
Click to expand...
Click to collapse
Not much, I have had no interest to spend time with this topic because I have been very busy IRL. After I get my new house renovated fully and get my job tasks done, I wont be spending much time with this project. Feel free to use any sources provided in this thread to further advance the subject.
But this wont go forward that much, if the GT-P6800 wont get official CM10.1 update...
It works?
Hello there, it's time to get this rolling somewhere.
This is a Development-Thread. Please don't post if you aren't a developer.
What this IS
This is a Development thread, a platform for developers to discuss the development of CyanogenMod for the G925F. It's made so that we can get this working, fix up the problems - because there will be severe ones - and achieve a working official Rom at some point.
At the moment it's @OldDroid and me with help, but it would be awesome if interested devs would join in so that we can make this a team effort.
In short, it's a Dev-Thread in a dev section.
Right now it doesn't work and I'm not sure that it will work.
What this IS NOT
This is NOT a working Rom. Not even close. I can only link you to the kernel repo and soon to device and vendor, as they are almost completed for a first try.
And yes, there is no download link for the Rom. Because there isn't anything you could download yet.
This is also NOT intended as a Q&A thread. Please don't ask if your variant will be supported, I will respond by trolling. Firstand only priority is to get this running, then we'll talk about variants.
And ETA is an evil word with no meaning here. I work slowly, deal with it
Where are we currently?
Much further than a day ago
Thanks to @OldDroid, we've teamed up
All the links you want (minus the download link :angel
device: (soon, almost complete)
https://gitlab.com/mythos234/device_samsung_zeroltexx
vendor:
https://gitlab.com/mythos234/vendor_samsung_zerolte
kernel:
https://gitlab.com/mythos234/zerolte-kernel-CM
Once available, buggy alpha builds will be posted here
///
vendor and device will soon be pushed to my github
Reserved
i'll join you ... also started working on cm12.1 for s6 edge 5 days ago (currently in england with my school class)
vendor is setup
OldDroid said:
i'll join you ... also started working on cm12.1 for s6 edge 5 days ago (currently in england with my school class)
Click to expand...
Click to collapse
Welcome aboard then
vendor is finally setup and good to go!
https://github.com/mythos234/vendor_samsung_zerolte
It's apparently not without some minor casualties, but we got it. Huge thanks to @RaymanFX, he's helping me, since I'm not that much into CM building yet and I'm also basing this project on his CM for the N910C, which's 5433 is darn similar to our 7420, so we got a pretty good base to begin with.
add me as participant to the repos ^^
https://github.com/OldDroid
OldDroid said:
add me as participant to the repos ^^
https://github.com/OldDroid
Click to expand...
Click to collapse
Done for all the 3 of them
Looks like I killed Bluetooth for now (lol). Other than that it's slow but steady progress.
mythos234 said:
Looks like I killed Bluetooth for now (lol). Other than that it's slow but steady progress.
Click to expand...
Click to collapse
What do you mean "killed"? Killed the chip or wiped the MAC addr. or something?
nasko_spasko said:
What do you mean "killed"? Killed the chip or wiped the MAC addr. or something?
Click to expand...
Click to collapse
I'm currently building the Rom with completely removed Bluetooth support
First Build is compiled and ready for a test.. But I can't install the zip. This would be hillarious if it wasn't so annoying
mythos234 said:
Besides I said it can't be installed Hard to test something you can't even install
Click to expand...
Click to collapse
I think that there was a mistake in the partition sizes.. /system was declared as 4.1GB, but it's only 3.6GB. Recompiling with a new value, should be able to flash it then
Good luck develop without documentation for exynos chipset.
But can you tell us more in details how porting works and what are the challenges with it.
Is it hard to develop a rom without samsung binary files and drivers? I know they are proprietary and closed soruce.
If just Samsung could be more developer friendly like Sony.
We can request source for closed binaries here, http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView, most likely they wont answer
Aircondition said:
Good luck develop without documentation for exynos chipset.
Click to expand...
Click to collapse
The lack of drivers makes this a fun exercise almost Where's be the challenge if everything was easy...?
Aircondition said:
Good luck develop without documentation for exynos chipset.
But can you tell us more in details how porting works and what are the challenges with it.
Is it hard to develop a rom without samsung binary files and drivers? I know they are proprietary and closed soruce.
If just Samsung could be more developer friendly like Sony.
We can request source for closed binaries here, http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView, most likely they wont answer
Click to expand...
Click to collapse
I can't say what the challenges here will be, since I couldn't manage to even flash it yet - Second build is compiling since hours now. For now it's using all the proprietrary stuff we managed to grab and some additional stuff from the 5433 CM. But without booting it's hard to tell what won't work and might present a challenge ^^ From what I saw it'll be tough to just get the modem running. The hard part is to write the drivers yourself
mythos234 said:
I can't say what the challenges here will be, since I couldn't manage to even flash it yet - Second build is compiling since hours now. For now it's using all the proprietrary stuff we managed to grab and some additional stuff from the 5433 CM. But without booting it's hard to tell what won't work and might present a challenge ^^ From what I saw it'll be tough to just get the modem running. The hard part is to write the drivers yourself
Click to expand...
Click to collapse
It's interesting that you can use drivers from 5433, which is a 32bit platform. Most drivers are not compatible when you switch from 32bit to 64bit if I am right?
Sent from my SM-G920F using Tapatalk
lch920619x said:
It's interesting that you can use drivers from 5433, which is a 32bit platform. Most drivers are not compatible when you switch from 32bit to 64bit if I am right?
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
As a base to know how to do it, obviously we can't just use drivers for a different chipset
Updated the /system size in the BoardConfig and at least it flashes. But it doesn't want to boot for some reason yet.
mythos234 said:
Updated the /system size in the BoardConfig and at least it flashes. But it doesn't want to boot for some reason yet.
Click to expand...
Click to collapse
If you have the 5.1.1 boot loader and are using 5.0.2 as a base. Sboot will not boot it. As a fyi. It checks Linux versions.
-Mr. X- said:
If you have the 5.1.1 boot loader and are using 5.0.2 as a base. Sboot will not boot it. As a fyi. It checks Linux versions.
Click to expand...
Click to collapse
Both is 5.1.1 and Sboot seems to clear the boot as well, everything seems to go fine, it just doesn't boot. :/ Trying with building the kernel during the build itself instead of using a prebuilt one and see how that goes
mythos234 said:
Both is 5.1.1 and Sboot seems to clear the boot as well, everything seems to go fine, it just doesn't boot. :/ Trying with building the kernel during the build itself instead of using a prebuilt one and see how that goes
Click to expand...
Click to collapse
I would personally flash an Engineering boot loader while doing this, to ensure version checking is not the issue.
--FOR MORE INFO AND NEWS ALWAYS CHECK MY LAST REPLY!--
Thanks for understanding!
PROJECT IS ABANDONED.
Regards,
Holy ****, finally. I cant try it out for my self cause i need to leave to malta tomorrow but i can try it later
MIUI Rom, finally!!!!
I hope they fix the bug as soon as possible
Again, the ROM is NOT bootable, I need logcats from you to fix the problem, hopefully.
So don't expect this to boot.
Thanks for understanding!
Try to take a look here Logcats
I hope to have helped
Giuseppe300715 said:
Try to take a look here http://https://forum.xda-developers.com/showthread.php?t=1726238
Click to expand...
Click to collapse
I cannot open the link. It gives me an error.
XTutorials said:
I cannot open the link. It gives me an error.
Click to expand...
Click to collapse
He meant this link https://forum.xda-developers.com/showthread.php?t=1726238
XTutorials said:
I cannot open the link. It gives me an error.
Click to expand...
Click to collapse
I just fix the connection
---------- Post added at 09:04 AM ---------- Previous post was at 08:50 AM ----------
[Universal] [Flashable] [Logcat] [Guide] So your test ROM build didn't boot
[UNIVERSAL][LOGCAT]How to get & read a logcat/ Troubleshoot your own issues!
That's all I've found and that can be useful for both this Rom and others that you will develop.
Thank you, but I know how to dump logcats. I asked you if you could provide me some logcats of the rom not booting from your device and send me.
Thank you.
XTutorials said:
The ROM is compiled, but it doesn't boot and me and @AymenDe7 need logcats.
I will provide a download link, but just in google drive so not much downloads will be allowed. Bootable version (if) will be released on androidfilehost.
https://drive.google.com/open?id=0Bx9qplihpe8YVUNZRTNnSFY1bkk
Full no reject source code:
https://github.com/aymende7/XTutorials_Miui8
For now I need logcats from you.
Thanks for understanding!
Click to expand...
Click to collapse
Here's my logcat. http://www117.zippyshare.com/v/WcWK3ksX/file.html
I think there's problem with OpenGL
06-13 10:04:20.297 2468 2468 E libEGL : load_driver(/system/lib64/egl/libGLES_mali.so): dlopen failed: library "/system/lib64/egl/libGLES_mali.so" not found
06-13 10:04:20.297 2468 2468 F libEGL : couldn't find an OpenGL ES implementation
--------- beginning of crash
Click to expand...
Click to collapse
And if you would copy libGLES_mali.so to /system/lib64/egl?
Would it work?
Thank you for your logcats. I will see what I can do.
How does it go with progress?
Should boot if you use custom kernel and copy&replace blobs
I am giving up on trying to fix that error message. I am trying to build AOSP 6 and then try again patchtom, hopefully I won't get that error.
I know how to get miui booted, making aosp is not enough, there is changes you need to play with them like .rej files and boot.img too experienced on my old s2 plus i9105p. as I got stuck at animation boot.
haky 86 said:
I know how to get miui booted, making aosp is not enough, there is changes you need to play with them like .rej files and boot.img too experienced on my old s2 plus i9105p. as I got stuck at animation boot.
Click to expand...
Click to collapse
MIUI ports were one of the most time-consuming ports. I'm not sure how does it look like today but I'm pretty sure it's identical to how it used to be. First you had to modify the ramdisk and then patch all java resourced and with a bit of luck you get bootable rom.
I'm really sick of seeing all those roms all based on 1 device tree which is not even fully functionall yet. People keep making "new" roms but all are actually the same, all have same list of non-working features. Just compiling different android distro with same device tree over and over.
XDA used to be place for original work and for people who put effort in their projects. Now kids keep spamming dev threads with copy&paste roms or useles threads.
lozohcum said:
MIUI ports were one of the most time-consuming ports. I'm not sure how does it look like today but I'm pretty sure it's identical to how it used to be. First you had to modify the ramdisk and then patch all java resourced and with a bit of luck you get bootable rom.
I'm really sick of seeing all those roms all based on 1 device tree which is not even fully functionall yet. People keep making "new" roms but all are actually the same, all have same list of non-working features. Just compiling different android distro with same device tree over and over.
XDA used to be place for original work and for people who put effort in their projects. Now kids keep spamming dev threads with copy&paste roms or useles threads.
Click to expand...
Click to collapse
Yeah. We have like 2 developers(one is a team) On this device. Haky and OpenKirin. And 6 "different" ROMs that all work the same, with the exception off the nougat FOMs, which have even more bugs.
lozohcum said:
MIUI ports were one of the most time-consuming ports. I'm not sure how does it look like today but I'm pretty sure it's identical to how it used to be. First you had to modify the ramdisk and then patch all java resourced and with a bit of luck you get bootable rom.
I'm really sick of seeing all those roms all based on 1 device tree which is not even fully functionall yet. People keep making "new" roms but all are actually the same, all have same list of non-working features. Just compiling different android distro with same device tree over and over.
XDA used to be place for original work and for people who put effort in their projects. Now kids keep spamming dev threads with copy&paste roms or useles threads.
Click to expand...
Click to collapse
I don't think that...I'm a kid...I make my own roms with my tree...:angel:
haky 86 said:
I don't think that...I'm a kid...I make my own roms with my tree...:angel:
Click to expand...
Click to collapse
I know man, I wasn't talking about you. I was talking in general. I know you're doing god work, despite I'm not developing anything since a long time I still read forum and follow what's happening.
Like @Vinnipinni said, 2 guys and 6 "different" roms. But all working the same.
Back in times people were more likely waiting for stable CM/AOSP before compiling bunch of other distros. Now it's just mess.
I really wish I could go back to developing for android devices, especially now when I have programming knowledge and experience.
Hi all:
This is a thread for my alternative LineageOS 14.1 roms for suzuran.
I'm building these roms from time to time for my own needs and I think other people should participate.
Since the "official" development of LineageOS 14.1 has been stopped, I decided to build a new version only if the Android security patch level has been changed or I've changed anything.
Download 2021-07-19
This is a 7z archive with the zip'ed rom and the md5 file in it. Please unpack this archive, copy the included two files somewhere to your device, reboot into TWRP and flash this zip file. Enable zip verification and md5sum checking. Maybe you have to rename the md5 file to *.md5sum; depending on the TWRP version you are using.
Kernel sources
Tree sources
Features:
OS Version: 7.1.2 Nougat
Kernel: Linux 3.10
New: Android security patch level: 5 June 2021
Using sony blob's from stock version 32.4.A.1.54
Important informations:
You should be familiar with general installation of custom roms.
Required for installation: TWRP 3.1.1 (or newer).
OR use my self built TWRP-version 3.5.2!
No need for making a clean install, but sometimes it helps a lot!
This rom is pre-rooted. For those who want to use magisk or any other rooting tool, you can easily remove this by flashing this file.
Use this rom at your own risk! It comes without any warranty! I'm not responsible for any damage! If you don't agree with that, don't try to flash this rom in any way.
Differences between my version and the "official" one:
Kcal Display Driver - Thanks to @GreyLeshy and @Sony user 16
Voltage Control - Thanks to @GreyLeshy and @Sony user 16
OMS-Support - Thanks to @nathanchance
Added F-Droid and UnifiedNLP! If you don't want this, simply de-install it.
I've included some little extensions like changelog and volume adjustment.
I've set maximum speaker volume to a higher value.
I've increased microphone gain.
I've increased all volume steps from 7 to 15.
I've changed the microfone gain to avoid echo in phone calls.
I've enabled data for MMS.
I've enabled MHL.
Not working:
VoLTE, VoWiFi
If you want to use encryption, you have to disable SIM PIN first!
One (last) request: Please don't ask for including any app. I won't do this, because I want to keep this rom as clean as possible.
Changelog
Troubleshooting:
If you're running into an error, please search in this thread if this error is already posted, before you post it again!
If not, I need a LOG to see what went wrong. Without a LOG I can't help you!
A LOG can be fetched by connecting the device with an USB cable to your PC and then by typing these commands line by line:
Code:
adb root
adb shell logcat -b all -d > logcat
Send my this LOG file via PM.
If you think this could be a SELinux related issue, please try to set the device to permissive mode first.
If the issue is gone, I need the policy file too (plus LOG). Fetch it by typing this line in a terminal:
Code:
adb pull /sys/fs/selinux/policy
If you stuck in a bootloop you can fetch a LOG with this trick:
Press the power button and the volume up button together until the device shuts down.
HOLD the power button.
Release the volume up button and press the volume down button immediately after releasing the volmue up button.
The device should start into TWRP recovery.
Tap on "Advanced", then on "Terminal" and enter these commands line by line:
Code:
cd sys/fs/pstore
cp * /sdcard
Send me the copied file(s), if any, via PM.
Nice
Berni-0815 said:
Hi @all:
First of all, please excuse my bad english... :angel:
They said I should create my own thread for my alternative LineageOS 14.1 roms for suzuran. Here it is.
I'm building these roms from time to time for my own needs and I think other people should participate.
Download
Kernel sources
Tree sources
OS Version: 7.1.2 Nougat
Kernel: Linux 3.10
Required for installation: TWRP 3.1.1
Important informations:
You should be familiar with general installation of alternative roms.
I've included some little extensions like changelog and volume adjustment.
There is no need to make a clean install, but sometimes it helps a lot!
Use it at your own risk!
Click to expand...
Click to collapse
Hi ! It would be great if u put out the advantage of yours vs with the official LOS
Berni i said before and i m saying again please make this topic a lineage based rom..
İnclude minimal app for google play store.
And maybe can add substratum inside.. or can be a default diffefent theme ..
I believe you can..
Thx bro.
ROBNX85 said:
Hi ! It would be great if u put out the advantage of yours vs with the official LOS
Click to expand...
Click to collapse
As I wrote: "I've included some little extensions like changelog and volume adjustment."
emosis said:
İnclude minimal app for google play store.
Click to expand...
Click to collapse
As I said a few days before: I don't want to include gapps! If somebody wants to use gapps, feel free to flash them separately. You can download them here. You need arm64 and 7.1 for suzuran.
And maybe can add substratum inside..
Click to expand...
Click to collapse
Substratum support is not longer available, because the devs have stopped their development for Nougat since august.
Berni-0815 said:
As I wrote: "I've included some little extensions like changelog and volume adjustment."
Click to expand...
Click to collapse
Add a basic ad-blocker too ?
Berni-0815 said:
As I said a few days before: I don't want to include gapps! If somebody wants to use gapps, feel free to flash them separately. You can download them here. You need arm64 and 7.1 for suzuran.
...
Click to expand...
Click to collapse
I agree gapps should not be included. It is easy enough to just flash it right after flashing the rom
I am thinking about official vs rom, I think the two roms are probably nearly identical. Probably the most important factor will be the frequency of updates.
PeppeBove said:
Add a basic ad-blocker too
Click to expand...
Click to collapse
You can use AdAway which is an open source host list based ad blocker. See https://adaway.org
PeppeBove said:
Add a basic ad-blocker too
Click to expand...
Click to collapse
I don't see a reason to bake something into the ROM when there are many apps that can do it.
I think something like Xposed-type tweaks being put into settings would be more appropriate. Alleviating the need for xposed. But I don't think it makes sense to load random apps into the ROM.
New version; please have a look at the first post
Berni-0815 said:
New version; please have a look at the first post
Click to expand...
Click to collapse
Awesome work, thank you so much! Flashing it now.
Just 1 question - do you know if encryption works on your builds?
I've never tried it. I've not so good experience with encryption on a stock rom; so I've decided not to use this feature at all!
Hi Bernhard.
Thanks for your hard work!
i have a question for you.... As i understand it you take all the changes/updates from the offifcial lienage and implement them into your own build. And add the changes as described in post 1.
Am i right about this?
I think that battery life is bad on the official compaired to the version you do.
Do you add battery improvements in your build?
Thanks in advance.
Torben 5247
torben5247 said:
Thanks for your hard work!
Click to expand...
Click to collapse
Oh, it is not so hard to do this, but, thank you! Sometimes I have to search a few hours or try (and revert) something, but in the end I've gotten everything to work as I like it to work.
As i understand it you take all the changes/updates from the offifcial lienage and implement them into your own build.
Click to expand...
Click to collapse
I'm using the LineageOS repositories from github as they are, that's right. I don't use my own repo's; nzzane is doing this AFAIK (Klick). A few weeks ago I'm using other repo's, because LineageOS had bad (will say: not working) sources for our devices.
And add the changes as described in post 1.
Am i right about this?
Click to expand...
Click to collapse
Yes! :good: One or two of my changes should be implemented into the "official" builds, but until now I don't understand how to use "commitments". Maybe in a few days... :angel:
I think that battery life is bad on the official compaired to the version you do.
Do you add battery improvements in your build?
Click to expand...
Click to collapse
No. Nothing like this.
On my own device battery life is about three days...
Hi,
PeppeBove said:
Add a basic ad-blocker too
Click to expand...
Click to collapse
emosis said:
İnclude minimal app for google play store.
And maybe can add substratum inside..
Click to expand...
Click to collapse
Like other persons, I don't want to have a lot of applications include in the rom. I want to choose the ones I use. This is one reason that made me come to alternative rom.
Another reason is that Lineage use less google s"hit" than stock rom.
So if you have the vision of more app and google stuff include, you better stay on stock. Alternative Roms offers me more freedom; but that's just my opinion...
This is prerooted? There are some of us out there that need to install certain apps before rooting.
Cerhio said:
This is prerooted?
Click to expand...
Click to collapse
Yes.
Berni-0815 said:
One or two of my changes should be implemented into the "official" builds, but until now I don't understand how to use "commitments".
Click to expand...
Click to collapse
I've just committed three of my changes. We'll see if they will be merged...
Berni-0815 said:
I've just committed three of my changes. We'll see if they will be merged...
Click to expand...
Click to collapse
The brightness settings? I hope so
What else?
Berni-0815 said:
I've just committed three of my changes. We'll see if they will be merged...
Click to expand...
Click to collapse
That's so great to hear, let's hope they get accepted.
Huge thank you for keeping this device alive Berni!