Hi , This was created so we can make ROMs for the extinct grand neo . Every ROM , even Oreo is there for plus model but nothing at all for this model, I request devs and can help in any way as I still have the phone
But I currently use xperia e3 with lineage OS 14.1 (7.1.2 Android)
Hello
RaghavTecki29 said:
Hi , This was created so we can make ROMs for the extinct grand neo . Every ROM , even Oreo is there for plus model but nothing at all for this model, I request devs and can help in any way as I still have the phone
But I currently use xperia e3 with lineage OS 14.1 (7.1.2 Android)
Click to expand...
Click to collapse
The device can be added to lineageos but I do not know.
I think someday i will learn how to compile rom, so i can compile LOS for this device, idk when, but maybe, could be great because i have 2 samsung galaxy grand.
But i think my computer need to be more powerful, so this can be impossible
I might try to get something working, but I don't promise anything
Wanted to do the same thing back in 2017 (see https://forum.xda-developers.com/showpost.php?p=73299951) but forgot about it. I'll pick up on the project and see how far can I take it.
knuxfanwin8 said:
I might try to get something working, but I don't promise anything
Wanted to do the same thing back in 2017 (see https://forum.xda-developers.com/showpost.php?p=73299951) but forgot about it. I'll pick up on the project and see how far can I take it.
Click to expand...
Click to collapse
I can test your rom if you compile one.
Thanks! I'll try to compile it today or tommorow.
---------- Post added at 08:39 AM ---------- Previous post was at 08:37 AM ----------
antoine62 said:
I can test your rom if you compile one.
Click to expand...
Click to collapse
Thanks! I'll try to compile it today or tommorow.
knuxfanwin8 said:
Thanks! I'll try to compile it today or tommorow.
---------- Post added at 08:39 AM ---------- Previous post was at 08:37 AM ----------
Thanks! I'll try to compile it today or tommorow.
Click to expand...
Click to collapse
I hope that you compile it today
Current project status: rebranded stuff to Lineage, and I'm getting "No matches for product: lineage_baffinlite" despite all files being in the right places.
Thaaaat's Android building for 'ya.
Some news?
antoine62 said:
Some news?
Click to expand...
Click to collapse
I guess?
Bad news is, I didn't go much further.
Good news is, I found out about postmarketOS. It requires a lot less work to get the base up and running, but it's possible that hardware support can be a problem.
Even better news: I might get a device for testing next week (and if not next week, then likely on Easter).
So, could anybody get CPU-Z and send me screenshots of all the tabs, just so that I can verify everything? (What I need the most is the screen resolution)
Once that will be done, I'll post a flashable ZIP (or a full heimdall compatible thing, we'll see).
knuxfanwin8 said:
I guess?
Bad news is, I didn't go much further.
Good news is, I found out about postmarketOS. It requires a lot less work to get the base up and running, but it's possible that hardware support can be a problem.
Even better news: I might get a device for testing next week (and if not next week, then likely on Easter).
So, could anybody get CPU-Z and send me screenshots of all the tabs, just so that I can verify everything? (What I need the most is the screen resolution)
Once that will be done, I'll post a flashable ZIP (or a full heimdall compatible thing, we'll see).
Click to expand...
Click to collapse
I dont have my samsung grand rn, srry
Got the resolution from GSMarena
Anyways, I did I quick test build with weston, just to see if it works. I definitively will get LineageOS 16.1 working soon, and possibly run some TWRP builds if necesarry.
Here are the files:
https://androidfilehost.com/?w=files&flid=291150
The pmos-samsung-baffinlite.zip file is a flashable ZIP file - flash it through TWRP. The tar.md5 is just the boot.img. As this post is being written, I'm still uploading the samsung-baffinlite.img which I assume is the rootfs only. (EDIT: It's done)
knuxfanwin8 said:
Got the resolution from GSMarena
Anyways, I did I quick test build with weston, just to see if it works. I definitively will get LineageOS 16.1 working soon, and possibly run some TWRP builds if necesarry.
Here are the files:
https://androidfilehost.com/?w=files&flid=291150
The pmos-samsung-baffinlite.zip file is a flashable ZIP file - flash it through TWRP. The tar.md5 is just the boot.img. As this post is being written, I'm still uploading the samsung-baffinlite.img which I assume is the rootfs only. (EDIT: It's done)
Click to expand...
Click to collapse
wait
Thid is the rom?
For the grand i9060?
antoine62 said:
wait
Thid is the rom?
For the grand i9060?
Click to expand...
Click to collapse
Not really, it's postmarketOS, which is basically pure Linux for Android devices (and doesn't have fully developed mobile capabilities yet). As I said, I'll be trying to get lineage os 16 builds working next (for real this time).
Oh, ok but this is for the i9060?
knuxfanwin8 said:
Not really, it's postmarketOS, which is basically pure Linux for Android devices (and doesn't have fully developed mobile capabilities yet). As I said, I'll be trying to get lineage os 16 builds working next (for real this time).
Click to expand...
Click to collapse
Thank you for your time trying to compile a rom for this device. I hope you might get positive results. I tried compiling, porting a rom, also failed didn't know what I did wrong. Hopes are on you my friend
I'm here to test the rom for you.
BREAKING NEWS: I no longer get that "cannot find product spec" error! Expect LineageOS 16 builds from whatever sources I was able to find soon, possibly around next week.
This is awsome If this old phone get android pie (with basic thing working, like RIL and wifi)
---------- Post added at 06:35 PM ---------- Previous post was at 06:30 PM ----------
Another thing: Where can i find how to compile a rom for a device that isn't officially suported?
Some more news: I've got my own Grand Neo for testing now!
The build's going well, at the moment I'm a bit stuck but will get everything sorted out eventually.
Device tree:
https://github.com/knuxdroid/android_device_samsung_baffinlite
antoine62 said:
Another thing: Where can i find how to compile a rom for a device that isn't officially suported?
Click to expand...
Click to collapse
You can follow the official build guide (this one). You'll have to add the device to the repo manifest:
- create ~/android/.repo/local_manifests/local_manifest.xml
- copy the following (replace information as needed):
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="github" fetch="https://github.com/" />
<project path="device/DEVICE MANUFACTURER/DEVICE CODENAME" name="GITHUB USER/android_device_DEVICE MANUFACTURER_DEVICE CODENAME" remote="github" revision="master" />
<project path="kernel/DEVICE MANUFACTURER/DEVICE CODENAME" name="GITHUB USER/android_kernel_DEVICE MANUFACTURER_DEVICE CODENAME" remote="github" revision="master" />
<project path="kernel/DEVICE MANUFACTURER/DEVICE CODENAME" name="GITHUB USER/android_kernel_DEVICE MANUFACTURER_DEVICE CODENAME" remote="github" revision="master" />
<project path="hardware/DEVICE MANUFACTURER" name="LineageOS/android_hardware_DEVICE MANUFACTURER" remote="github" revision="master" />
</manifest>
You can find the repositories on github, replace the name="GITHUB USER/android_device_DEVICE MANUFACTURER_DEVICE CODENAME" with the link to the repository (without https://github.com/) and make the path match the name (for example android_device_samsung_baffinlite becomes path="device/samsung/baffinlite").
There are many better tutorials than this online in case you don't understand something (I'm pretty bad at explaining things )
Relatively recent?
Rip, my pc is very old xD
Like 6-7 years old
---------- Post added at 05:25 PM ---------- Previous post was at 05:18 PM ----------
Android 9 rom need twrp 3.2 i think?
If yes, then we need a new twrp version
Related
It's question me for a long time. All the custom rom's building instruction say that "Your device should already be running the branch of CyanogenMod you wish to build your own version of for the extract-files.sh script to function properly. If you are savvy enough to pull the files yourself off the device by examining the script, you may do that as well without flashing CyanogenMod first."
But where is the "first" proprietary blobs came from? I know for the nexus device we can get the driver from
developers.google.com / android / nexus / drivers
But how about the others? How can we get the kitkat proprietary blobs for "galaxy nexus" and other devices for the first time build?
ps: I am not sure if it is appropriate to post this question here. But I do not know where to ask... sorry if this is in appropriate. And also sorry for my bad English..
https://github.com/DonkeyCoyote
So for my i9100 (Samsung SII (intl)) I had to add
Code:
<project path="vendor/samsung" name="DonkeyCoyote/proprietary_vendor_samsung" remote="github" revision="android-4.4" />
inside the
Code:
<manifest> ... </manifest>
tags in
Code:
.repo/local_manifests/local_manifest.xml
FatMinMin said:
It's question me for a long time. All the custom rom's building instruction say that "Your device should already be running the branch of CyanogenMod you wish to build your own version of for the extract-files.sh script to function properly. If you are savvy enough to pull the files yourself off the device by examining the script, you may do that as well without flashing CyanogenMod first."
But where is the "first" proprietary blobs came from? I know for the nexus device we can get the driver from
developers.google.com / android / nexus / drivers
But how about the others? How can we get the kitkat proprietary blobs for "galaxy nexus" and other devices for the first time build?
ps: I am not sure if it is appropriate to post this question here. But I do not know where to ask... sorry if this is in appropriate. And also sorry for my bad English..
Click to expand...
Click to collapse
In general, the blobs are first obtained by pulling all of the contents of /system from a device running stock.
Sometimes the blob archive winds up being a bit of mix-and-match of stuff from multiple sources...
It's a real mess and unfortunately there is no way to simplify the mess without raising some potential legal issues, as blobs are a bit of a grey area here.
FatMinMin said:
It's question me for a long time. All the custom rom's building instruction say that "Your device should already be running the branch of CyanogenMod you wish to build your own version of for the extract-files.sh script to function properly. If you are savvy enough to pull the files yourself off the device by examining the script, you may do that as well without flashing CyanogenMod first."
But where is the "first" proprietary blobs came from? I know for the nexus device we can get the driver from
developers.google.com / android / nexus / drivers
But how about the others? How can we get the kitkat proprietary blobs for "galaxy nexus" and other devices for the first time build?
ps: I am not sure if it is appropriate to post this question here. But I do not know where to ask... sorry if this is in appropriate. And also sorry for my bad English..
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/drivers#grouper
Here are all the stock blobs, Extract to your build folder then run the scripts in bash
They will then after accepting the license install to the correct vendor location.
( i just learned this last week )
Is there any way how you can get blobs for not so popular devices?
Like Cat S50? The Android is compiled by "Bullitt Group ltd" AFAIK.
Also I know HTC One mini 2 has the same chipset, is it possible to use the one's from that device?
barkley128 said:
Is there any way how you can get blobs for not so popular devices?
Like Cat S50? The Android is compiled by "Bullitt Group ltd" AFAIK.
Also I know HTC One mini 2 has the same chipset, is it possible to use the one's from that device?
Click to expand...
Click to collapse
In general, if you're doing the bringup for a given device, you pull the blobs from a stock firmware for that device, then try to integrate them. Sometimes in the end you wind up grabbing blobs from another device (such as Adreno GPU blobs from a Nexus or a newer device with same chipset), but people always start with the stock firmware and go from there.
Incase anyone is looking for the same
See this thread here. http://forum.xda-developers.com/showthread.php?t=2794413 :good:
Hi, figured this was the best place to post this as I can't post in the CM maintainers thread yet.
I'm experimenting with building Cyanogenmod 11 from source for my Note 3 (hlte), with the ultimate aim of learning to contribute to CM. I've been following along with the CM wiki page for building for hlte but have hit a bit of a roadblock.
About 10 minutes into the brunch hlte make process, I'm getting a weird error:
make: No rule to make target `vendor/samsung/hlte/proprietary/lib/cdma/libsec-ril.so',
needed by `/home/user/CM11/system/out/target/product/hlte/system/lib/cdma/libsec-ril.so'. Stop.
I ran the extract-files.sh to get the proprietary blobs, twice, so I'm fairly certain that isn't the problem. My phone model is the international variant (hltexx) though and I think the error might be something to do with my phone possibly not having the CDMA blobs required for the build to complete. Does anyone know how I can work around this? My phone was/is running CM11 when I extracted the proprietary blobs.
i have this exact problem. i have the tmobile note 3 and am following the CM wiki to build
http://wiki.cyanogenmod.org/w/Build_for_hlte
You can just pull the necessary files from TheMuppets repo in github. No need to extract from your phone.
That wiki page needs to be updated to mention this error. It still occurs even after running extract-propietary.sh on my hlte running the 18/4 nightly. Also, the repo init command incorrectly specifies to use the cm10.2 branch rather than the cm11.0 branch. I cannot figure out how to edit the page though, only add comments Thanks jisoo I'm going to clone that repo for the time being and I'll report back if it works
jisoo is right. Pull from TheMuppets:
https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-11.0/hlte
I am a noob aswell but intend to create a local_manifest file with the following:
<manifest>
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-11.0" />
</manifest>
It will download all the proprietary blobs (I hope that is the right terminology), then you can use the hlte one. I don't know git enough to get it to just download the hlte folder, if anyone does and can help I would be grateful?
Hi,
Since I don't have permissions to post under development forum, I have to post this here
This is my unofficial compilation of PAC-ROM Lollipop.
I did this because there is no lollipop pac for yuga.
Download:
New from 28.03.15:
http://d-h.st/z76p
New MD5:
b408191649b3d35e52589b2b76020256
Old one:
http://d-h.st/HMsN
Old MD5:
1d271e26fdf2225cc0ca95b4e6e1a889
Note for mods: Can you please move this thread to development section?
Here is my local_manifest:
Code:
<project name="Pinky-Inky-and-Clyde/proprietary_vendor_sony" path="vendor/sony" remote="github" revision="cm-12.0"/>
<project name="CyanogenMod/android_device_sony_common" path="device/sony/common" remote="github" revision="cm-12.0"/>
<project name="CyanogenMod/android_device_sony_yuga" path="device/sony/yuga" remote="github" revision="cm-12.0"/>
<project name="CyanogenMod/android_device_sony_qcom-common" path="device/sony/qcom-common" remote="github" revision="cm-12.0"/>
<project name="CyanogenMod/android_device_sony_fusion3-common" path="device/sony/fusion3-common" remote="github" revision="cm-12.0"/>
<project name="CyanogenMod/android_device_sony_msm8960-common" path="device/sony/msm8960-common" remote="github" revision="cm-12.0"/>
<project name="CyanogenMod/android_kernel_sony_apq8064" path="kernel/sony/apq8064" remote="github" revision="cm-12.0"/>
<project name="CyanogenMod/android_hardware_sony_DASH" path="hardware/sony/DASH" remote="github" revision="cm-12.0"/>
Sorry for my English
No screenshots ? :v
It's just like any other PAC-Rom
So whats working and whats not?
I don't see any bugs or something strange here. I'm using this ROM as daily driver
Repository synced and new ROM compiled!
Updated ROM and MD5 added to OP!
dzialo88 said:
Repository synced and new ROM compiled!
Updated ROM and MD5 added to OP!
Click to expand...
Click to collapse
great work! So far so good! :fingers-crossed:
Good Rom.
Thanks man,gonna take this AS daily driver too
Thanks to @Schneiderle who said me that there is this awesome lookin Rom
Btw so "things" Mike USB otg (EG with controller) and (native) screen mirroring is working ? Thanks !
Will report!
@dzialo88
Can you please edit the Start Post, Pac-Rom has since pretended that I know what kernel sources have taken you.? Github link would be very nice
@Cr33D OrB
I don't use screen mirroring but I got cheap USB OTG cable and it's working pretty good :good:
@Schneiderle
Added local_manifest to OP. Can be? :highfive:
@dzialo88
OK,USB otg working
So u dont know if scm is workng?..
Hmm.no prob ;p
Then i will have a look at it and will See if it works or not!
Pls give me info about it's working or not :highfive:
Installed rom CLEAN flash and seems that there no root Privilegs although actived in devoptioms and supersu and superuser..
Whatsapp is FC too.
Solution?
EDIT : Isnt this Rom Pre-rooted ?
Cant gain root access .. @dzialo88
Go into developer settings. There is root option. By default is no root
root is enabled but it's not
Yeah,same there is no root
Btw USB otg using controller AND screen mirroring not Working..
Man,thats no beta
Any Update News ?
Schneiderle said:
Any Update News ?
Click to expand...
Click to collapse
Now I'm going to provide pacman5.1 but many features aren't merged yet so please be patient
I'm gonna recover my Kitkat backup.
The current build doesn't suit my expectations. It doesn't feel ripe at the current state.
I have a massiv battery drain and I don't know why. Compared to the KitKat image, my phone dies in just a quarter of the time. According to Wakelock Detector, my phone was 87% of the time awake because msm_hsic_host had a wakelock. I also flashed Super Su (due to a missing management delivered by the ROM?) that kept a screen wakelock (wtf? my screen was definitly off!).
Another bug: When installing a self signed certificate, a gesture is recognized as a valid lock, but the certificate fails to install with "certificate not installed". I had to set a PIN to install my certificate. Also I'm missing different pattern sizes for the lockscreen.
Also: My wifi and mobile are always marked with a exclamation mark so I can't see, if I'm using 2G or 3G (possibly because I have no Gapps installed). I'm also missing the quick settings tile for switching between 2G and 3G. There's just a toggle for 4G.
The battery bar isn't visible if it's configured top or bottom the navbar.
That's everything that I have on my mind. Maybe it could scale the UI (notifcation drawer) better like the Settings app does, if the dpi value is lower (see image). At a value of 240 dpi, I have to draw my gesture on a box of 5x5 cm. Also the SIM-PIN request is small. (see second image). I would be really nice, if something could happen to scale them up to use the available space.
Everything else I'm using seems to run stable and fine. So nice work.
I'm going to try an Android 5.1 build when available. So I hope the era of Xperia Z isn't over already and we get some more updates by enthusiastic devs.
/edit: I also missed the PacPerformance manager
- I don't like the nearly useless CM Recovery
- I killed my baseband while undoing my upgrade
I'm testing 5.1 now (It compiled with source from 5.0 ). That's true CM Recovery is useless You should flash this in FOTAKernel partition http://forum.xda-developers.com/xperia-z/orig-development/recovery-teamwin-recovery-project-t2982889 . I only compiled this ROM, I don't know how to remove bugs :v
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.1 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
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.
*
*/
CyanogenMod 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). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Important information:
This thread is for Unofficial CyanogenMod 13.0 builds for chagallltetmo (SM-T807T). 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
Installation
First time flashing CyanogenMod 13.0 on your device, or coming from another ROM?
Download the zip(s)
Install the T805 TWRP Recovery
Make sure you are on the latest bootloader (Lollipop 5.0.2)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash CyanogenMod
Install the Google Apps addon package (Optional)
Reboot
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
Downloads
CyanogenMod:
4/28 Build
Google Apps:
http://opengapps.org/- thanks to the OpenGapps team!
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Source:
Kernel: https://github.com/CM-Tab-S/android_kernel_samsung_klimtwifi
Device Tree: https://github.com/CM-Tab-S/android_device_samsung_chagallltetmo
Credits:
@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)
@suhridkhan (for doing all of the on device testing for chagallltetmo)
Bugs:
DRM content in Google Play Movies does not play
Mic is quiet
Mobile Network is not fully working, your phone number, simcard, baseband are found but it can not connect to T-Mobile/AT&T yet
This build is very similar to T805 but i have set the default apn to T-Mobile LTE, to get the mobile network even partially working (Did not work at all on T805 builds) i have had to replace almost all of the ril proprietary blobs, i am also going to have to probably completely rewrite the ril interface we will have to see.
My Local manifest this will allow you to build any of the tab s variants
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CM-Tab-S/android_device_samsung_klimtwifi" path="device/samsung/klimtwifi" remote="github" />
<project name="CM-Tab-S/android_device_samsung_klimtlte" path="device/samsung/klimtlte" remote="github" />
<project name="CM-Tab-S/android_device_samsung_chagallwifi" path="device/samsung/chagallwifi" remote="github" />
<project name="CM-Tab-S/android_device_samsung_chagalllte" path="device/samsung/chagalllte" remote="github" />
<project name="CM-Tab-S/android_device_samsung_chagallltetmo" path="device/samsung/chagallltetmo" remote="github" />
<project name="CM-Tab-S/android_kernel_samsung_klimtwifi" path="kernel/samsung/klimtwifi" remote="github" revision="deathly_cm-13.0" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
<project name="CyanogenMod/android_hardware_samsung_slsi-cm_exynos" path="hardware/samsung_slsi-cm/exynos" remote="github" />
<project name="CyanogenMod/android_hardware_samsung_slsi-cm_exynos5" path="hardware/samsung_slsi-cm/exynos5" remote="github" />
<project name="CM-Tab-S/android_hardware_samsung_slsi-cm_exynos5420" path="hardware/samsung_slsi-cm/exynos5420" remote="github" />
<project name="CyanogenMod/android_hardware_samsung_slsi-cm_openmax" path="hardware/samsung_slsi-cm/openmax" remote="github" />
<project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" />
<project name="deadman96385/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-13.0-common" />
<remove-project name="platform/prebuilts/qemu-kernel" />
<project path="prebuilts/qemu-kernel" name="platform/prebuilts/qemu-kernel" clone-depth="1" remote="aosp" revision="refs/tags/android-6.0.1_r31" />
</manifest>
Mine just in case
Haha I had the download link for this yesterday
for those who are going to give it a shot, rom is fast and quite usable. But you need some precautions.
use Banks gapps package. opengapps giving problems.
you shall have to flash the rom and gapps at the same time. Do not boot into rom, if you are going to need gapps.
During the setup process keep the tablet in portrait mode. If you go landscape, the screen will freeze.
OMG Finally Marshmallow on the T807T!
I do need data to fully work before I flash this but i'd like to say thanks for getting this to our devices!
Wow! So happy right now!! Thank you for putting in the work for this. I was just about to downgrade to Lollipop but no more!
So I do have mobile data fully functioning, although I am using opengapps. I installed the rom as noted and when the play store wouldn't allow me to download content I went back into recoevery and wiped data and cache and reinstalled the same gapps and had success. So far the only problem I'm having is with bluetooth. It's only with the S Mouse. I have the keyboard fully functioning though. Im currently unable to attach my logcat file but will do so later. This is one line that sticks out "04-30 14:30:34.307 E/EventHub(3546): could not get driver version for /dev/input/mouse0, Not a typewriter". Will try and upload a complete log later.
Thanks again! I'll be happy to help out in the process.
metiCkOn3 said:
Wow! So happy right now!! Thank you for putting in the work for this. I was just about to downgrade to Lollipop but no more!
So I do have mobile data fully functioning, although I am using opengapps. I installed the rom as noted and when the play store wouldn't allow me to download content I went back into recoevery and wiped data and cache and reinstalled the same gapps and had success. So far the only problem I'm having is with bluetooth. It's only with the S Mouse. I have the keyboard fully functioning though. Im currently unable to attach my logcat file but will do so later. This is one line that sticks out "04-30 14:30:34.307 E/EventHub(3546): could not get driver version for /dev/input/mouse0, Not a typewriter". Will try and upload a complete log later.
Thanks again! I'll be happy to help out in the process.
Click to expand...
Click to collapse
what! you have mobile data? how?
I am not having any data here.
suhridkhan said:
what! you have mobile data? how?
I am not having any data here.
Click to expand...
Click to collapse
I switched to the ims apn, which then kicked back to the tmobile lte apn and data kicked on. I also disabled data roaming, maybe that played a part.
So I have an update. It looks like my apn was switching to a net 10 apn and giving me a connection under that apn, maybe I had data roaming on at that point in testing. To test this theory I have deleted all my apns but my tmobile us lte apn and I no longer get an LTE signal, mms does work however. I did edit the apn to match tmobile's recommeded settings for android tablets (magenta emploee here). Will keep testing.
UPDATE: Okay I got a connection and it stays for the most part. It disconnects if I put the tablet to sleep. A quick workaround is to disconnet and reconnect data. I will upload a screenshot of the settings I'm using.
metiCkOn3 said:
So I have an update. It looks like my apn was switching to a net 10 apn and giving me a connection under that apn, maybe I had data roaming on at that point in testing. To test this theory I have deleted all my apns but my tmobile us lte apn and I no longer get an LTE signal, mms does work however. I did edit the apn to match tmobile's recommeded settings for android tablets (magenta emploee here). Will keep testing.
UPDATE: Okay I got a connection and it stays for the most part. It disconnects if I put the tablet to sleep. A quick workaround is to disconnet and reconnect data. I will upload a screenshot of the settings I'm using.
Click to expand...
Click to collapse
Can you get a log of you having an active data, going to sleep and then waking back up? easiest way is to download syslog give it root and then do the proccess. Then upload the zip anywhere you like.
Edit: Also you would probably know does the T-Mobile variant have the ability to make calls on stock? I know T805 and T705 can but they are international devices.
Edit2: I also will see if i can enable a few more mouse drivers in the kernel, bluetooth is a constant issue currently across all the tab s variants
deadman96385 said:
Can you get a log of you having an active data, going to sleep and then waking back up? easiest way is to download syslog give it root and then do the proccess. Then upload the zip anywhere you like.
Edit: Also you would probably know does the T-Mobile variant have the ability to make calls on stock? I know T805 and T705 can but they are international devices.
Edit2: I also will see if i can enable a few more mouse drivers in the kernel, bluetooth is a constant issue currently across all the tab s variants
Click to expand...
Click to collapse
To answer your question about phone calls, I can't remember to be honest. It's been a year almost since we sold it and I only had stock for a day, but with all our tablets we disable the ability to call so I would imagine it DOES NOT have the ability to make calls. I can flash back to stock and check for you if you need.
Here's the log of the data disconnect and the bluetooth fail. I was wrong about the sleep disconnecting data, it was just a coincidence. Regardless, here is the log. Let me know if you need more testing.
Anyone know if this works with t807p (sprint LTE variant)??
Sent from my SM-T807P using XDA-Developers mobile app
Data Works Now
I changed mine to the same ims apn and data works with not issues now. I did a speed test I am getting about 19mbps at 2bars of lte. so not bad. So far so good.
metiCkOn3 said:
I switched to the ims apn, which then kicked back to the tmobile lte apn and data kicked on. I also disabled data roaming, maybe that played a part.
Click to expand...
Click to collapse
chargerfn909 said:
Anyone know if this works with t807p (sprint LTE variant)??
Sent from my SM-T807P using XDA-Developers mobile app
Click to expand...
Click to collapse
This will not work on the sm-t807p sadly that variant has a snapdragon soc.
wanpa78 said:
I changed mine to the same ims apn and data works with not issues now. I did a speed test I am getting about 19mbps at 2bars of lte. so not bad. So far so good.
Click to expand...
Click to collapse
Nice! Glad I could help a little. I used to port miui & cm to the droid & droid 2 but quit because I had too much learning to do and not enough time . Anyway, I'm really looking forward to future dev of this rom. I'm really hoping for full s-mouse support, although I'll take any mouse support.
Very pleased to see work progressing on this. We need to make this thread get more views!!
Great work and when I get a free day (if ever lol) I will load it up and see what I can help with.
Sent from my SM-N920T using XDA-Developers mobile app
deadman96385 said:
This will not work on the sm-t807p sadly that variant has a snapdragon soc.
Click to expand...
Click to collapse
Damn...That variant is like the curse of all tablets in terms of modding...lol. Thanks
chargerfn909 said:
Damn...That variant is like the curse of all tablets in terms of modding...lol. Thanks
Click to expand...
Click to collapse
Yeah they have it worse then the 807t. At least we can run some roms with the stock kernel.
Sent from my SM-N920T using XDA-Developers mobile app
NXLTrauma25 said:
Yeah they have it worse then the 807t. At least we can run some roms with the stock kernel.
Sent from my SM-N920T using XDA-Developers mobile app
Click to expand...
Click to collapse
Sadly, I am "they" :*( lol
Hello developers!
I am a newbie to XDA and also a newbie to ROM development, so if I am doing anything wrong, please do tell me. I own a Motorola Moto G4 Plus and I am very ready to invest as much time as needed in building and creating ROMs for this phone.
I am currently building LineageOS for this phone, and once that is done, I want to try my hand at porting Lineage 16 to this device. I had recently successfully built the cm-14.1 branch for this device (which seems to be the only official build for athene, see the LineageOS Wiki https:// wiki.lineageos.org/ devices/athene/ build#initialize-the-lineageos-source-repository). Now, I downloaded the code for LineageOS 15.1 onto my Linux computer (running Ubuntu 19.04) and have tried to build it.
Steps I took to build -
- Initialised repo with repo init.
- Synced the repository to my Linux computer with
Code:
repo sync -c --no-tags --no-clone-bundle -j24
- Created .repo/local_manifests/roomservice.xml for the device tree, kernel, etc. with the following content:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_motorola_athene" path="device/motorola/athene" remote="github" revision="lineage-15.0" />
<project name="LineageOS/android_kernel_motorola_msm8952" path="kernel/motorola/msm8952" remote="github" revision="lineage-15.0" />
<project name="TheMuppets/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="lineage-15.0" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="lineage-15.0" />
<project name="LineageOS/android_external_bson" path="external/bson" remote="github" />
<project name="LineageOS/android_external_stlport" path="external/stlport" remote="github" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" />
</manifest>
- Ran
Code:
repo sync -c -j24
- Then ran
Code:
export ROOMSERVICE_BRANCHES="lineage-15.0"
to specify a fallback branch
- Ran
Code:
source build/envsetup.sh
- Ran
Code:
breakfast athene
The command ran successfully, no errors until now.
- Then ran
Code:
brunch athene
This is where the problems started popping up. I got errors while building in the following places -
(Treat .(dot) as my source dir)
ERROR 1 - In out/soong/make-vars(don't remember correct file name) - Still get it after
Code:
make clobber[\CODE], I have to always comment line 692 which throws the my-check error to suppress it.
ERROR 2 - Couple of old CyanogenMod dependencies and packages which I managed to get past after messing about with the ./device/motorola/athene/BoardConfig.mk file.
ERROR 3 - Errored out because BOARD_KERNEL_IMAGE_NAME was not defined, finally found an old XDA thread for the 15.1 ROM that told me that I had to set that to zImage in device/motorola/athene/BoardConfig.mk
ERROR 4 - In file ./system/core/init/init.h - Could not find <android-base/chrono_utils.h>, Could not find <selinux/label.h> - Got rid of it by putting in relative file paths and also modifying the ./system/core/init/Android.mk's LOCAL_C_INCLUDES to have relative file paths.
ERROR 5 - In file system/core/adb/daemon/main.cpp, system/core/base/include/android-base/macros.h: Cannot identify arraysize(groups).
ERROR 6 - In file system/core/adb/daemon/main.cpp - Use of undeclared identifier 'AID_UHID'
I can try to fix these errors, but I feel that there must be some branch/fork of the LOS15.1 code that must have all these issues fixed. If anyone has any pointers regarding this or the errors, I would be very grateful.
Thanks in advance,
gamemaker1
I don't believe Lineage 15 or 15.1 ever made it to official status. LOS 14.1 was the last official rom for athene that I know of. You might take a look at this roomservice file and other noteworthy things.
https://forum.xda-developers.com/showpost.php?p=81772343&postcount=348
I've just started building myself and have built LOS 14.1 for a couple unsupported devices (atrix hd and razr hd). Also just started trying to build 16.0 for the old Razr HD but have quite a task ahead of me. Hope the link helps and good luck.
Wheels564 said:
I don't believe Lineage 15 or 15.1 ever made it to official status. LOS 14.1 was the last official rom for athene that I know of. You might take a look at this roomservice file and other noteworthy things.
https://forum.xda-developers.com/showpost.php?p=81772343&postcount=348
I've just started building myself and have built LOS 14.1 for a couple unsupported devices (atrix hd and razr hd). Also just started trying to build 16.0 for the old Razr HD but have quite a task ahead of me. Hope the link helps and good luck.
Click to expand...
Click to collapse
Ok, thanks! I just saw the link, it seems good. Will try it out today and let you know the result.
@Wheels564 Thanks a lot! You really made my day - the extra dependencies in the roomservice.xml got my build done in less than 40 minutes.
From here, I want to get (LOS 15.1 with some extra features of mine, maybe I could cherry pick some features from HavocOS or AEX) an official build out, maybe become an official contributor. If you have any tips about this, please do let me know.
Once again, thanks a ton for your timely help!
Regards,
gamemaker1
gamemaker1 said:
@Wheels564 Thanks a lot! You really made my day - the extra dependencies in the roomservice.xml got my build done in less than 40 minutes.
From here, I want to get (LOS 15.1 with some extra features of mine, maybe I could cherry pick some features from HavocOS or AEX) an official build out, maybe become an official contributor. If you have any tips about this, please do let me know.
Once again, thanks a ton for your timely help!
Regards,
gamemaker1
Click to expand...
Click to collapse
No problem at all. The only thing about LOS 15.1 is that Lineage will never make it official. They've dumped all the rest of the phone on 15.1 because of repo changes I believe. Check here: https://review.lineageos.org/269773
I'm sure they will continue to submit security patches just like 14.1. Looks like the only way to become official is to jump to 16.1. It looks like developers have had issues with athene on LOS 16.1. Glad you were able to build the rom and good luck with future projects.