Testing Thread - Moto G4 Play ROMs, Kernels, Recoveries, & Other De

This is just a testing thread for who wants to help in development, since not many users use Telegram, i will be posting my test builds here.
THERE WILL BE ONLY ONE TEST AT A TIME IN THE SECOND POST.
All discussions should be limited to this thread only, no pm.
Offitopic should be minimal as possible.
All reports should be with logs.
Don't report any issues which has been previously reported ( two to three reports are okay ) ( doesn't matter if same or different person ).
Thx.

Los 15 new build
Based on squid sources with updated IMS blobs
Check the network with all way you can
Go to network setting > enable enhanced 4g mode
Give logs when doing that.
https://mega.nz/#!pjgnyYwJ!r5xtD-x5E6ac3V6NIc-pvuYPtkYt8VLMy2xkk2Zjt38

Reserved

Added new build
See #post2

Related

MIUI.us 2.12.7 Ruby Pending Release

I do apologize for the early release of my ROM, in my opinion its an Alpha stage at the moment due to the fact it has no "Network Data". Which to me is a deal breaker.
List of known bugs:
-No Network Data (You can still make/receive calls & text)
-On first boot you will get a couple of FC's for Network Location (I think)
-Setting of Ringtones (I haven't bothered to seek a solution)
-MiHome is a Beta (It has Chinese mixed in, used this one as it was a simply solution to constant FC)
-Themes (Need to create a directory /data/system then setting proper permission's)
-Browser (Desktop mode?)
-Several apps still have Chinese (least of my concerns)
-Any bugs not mentioned in the latest unOfficial CM10
I do feel like the Data issue is a Framework problem
I had intended to release the ROM to a select few and get there opinion or suggestion of a solution. But decided to wait at the last minute yesterday after posting on Dev-Host, due to a conversation with the original MIUI I made the port from. He has the exact same bug with his port and spent a month attempting to correct the problem. The port he came from does not have the bug and I'm suppose to receive a copy of it soon. To restart the project from the original Port, not the Port of an Original ROM that is MIUI officially supported.
I do expect to have a complete rework within a day or two from the Original MIUI.
I'm going to attach a logcat & if a developer has time or would be interested in a link to the ROM I would happily share that with them.
A bit of my background is that I once upon a time developed for Motorola Cliq 2 and had a couple of ROM's, Mod's, Themes for it a few years back, also a Moderator for a Forum for the Cliq 2. Due to schedule changes I've gotten away from developing because of that, and had hoped to once again contribute to the android community.
CREDITS:
sportsstar89 for his work aswell and bringing hope to the device
dcacklam for all the hard work on the CM10 audio/bluetooth bugs
chiragkrishna for his allowing his work to give reboot into recovery/bootloader
cyanogenmod
MIUI
Extra special "Thanks" for letting me use their ROM to port ZeRo2o9 &
rafyvitto

CM10.2 AT&T/TELUS UNOFFICIAL

THIS BUILD IS ONLY FOR PEOPLE WHO WAN'T TO POINT OUT BUGS AND OTHER ISSUES THAT I HAVE NOT MENTIONED PLEASE DON'T COMMENT AND SAY ZOMG WHY DOESN'T CALL WORK OR STUPID CRAP LIKE THAT! AGAIN TESTING ONLY!!​
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. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
IMPORTANT INFORMATION
We'll not support users and answer questions from users which:
- are running a custom kernel
- have flashed mods
- modified system files
- didn't follow our intructions word by word
- are unfriendly
Even if you tell us that your problem is not related to your custom kernel /mod / magic => WE DON'T CARE!
Your mod => your problem!
CHECK KNOWN ISSUES IN SECOND POST
Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/
First time installing CyanogenMod 10.2 to your ONE X+, or coming from another ROM:
- Read known issues ans FAQs
- Make sure you're running a proper working ClockworkMod-Recovery
- Copy GApps and CM10.2 ZIPs to your SDCard
- Boot into HBOOT (hold Volume Down at boot)
- Flash the boot.img
- Fastboot flash boot boot.img
- Reboot into recovery via the bootloader menu
- Flash CM10.2 zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
DOWNLOAD:
Google Apps:
http://goo.im/gapps
ClockworkMod Recovery:
http://forum.xda-developers.com/showthread.php?t=2074396
If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
Open-Source doesn't mean Out-of-Respect!!!
XDA:DevDB Information
[ROM] CM10.2 AT&T/TELUS , ROM for the HTC One X+
Contributors
Lloir, h8rift
Source Code: https://github.com/evitareul
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.1.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2013-11-28
Last Updated 2014-11-19
List of stuff that IS working currently (not released and no eta)
Display
Audio
MTP
Camera
Microphone
GPS Borked
Ril\GSM
WIFI Now borked
Bluetooth
NFC​
Reserved
CHANGELOG
Code:
18/2/14
Fixed call audio, all it was, was a super hard to find error which said which permission it was
Fixed Data\gsm
28/11/13
inital testing release
In call is 100% buggered
GPS is trashed
Camera works (if gps is turned off)
Most recent CM source
PLEASE enable the Xda 2013 theme to view this thread correctly, as it is a DEVDB thread.
which enables you to see the downloads section
Q&A
Bug reports
Reviews
Screenshots
ALL questions > Q&A and NOT into this thread
Bug reports > Bug reports tab, with a logcat
Once all the kinks are sorted, this will be pushed to OFFICIAL CM.
If we stumble onto an issue, you want us to send the report?
Update: Been using it for a little under 3 hours, with a mix of Wi-Fi and can confirm that Data works in San Antonio Texas, it's been amazing. After everything settled in and downloaded all my apps, I installed TricksterMod to use the Interactive Governor, it runs very smooth. In addition, will confirm that both SMS & MMS Text messaging works, and Wi-Fi Tethering works. Thank you SO Much LLoir and everyone who is working on this. It really is amazing. I can't say that enough. Okay, just got done trying my Bluetooth headset, audio on games works as for music as well, but alas sadly not for calls, however, I am going to try a wired headset to see if that works.
sledgeharvy said:
If we stumble onto an issue, you want us to send the report?
Update: Been using it for a little under 3 hours, with a mix of Wi-Fi and can confirm that Data works in San Antonio Texas, it's been amazing. After everything settled in and downloaded all my apps, I installed TricksterMod to use the Interactive Governor, it runs very smooth. In addition, will confirm that both SMS & MMS Text messaging works, and Wi-Fi Tethering works. Thank you SO Much LLoir and everyone who is working on this. It really is amazing. I can't say that enough. Okay, just got done trying my Bluetooth headset, audio on games works as for music as well, but alas sadly not for calls, however, I am going to try a wired headset to see if that works.
Click to expand...
Click to collapse
yes please ALL bugs, please make sure you have the xda 2013 theme on (bottom left corner on the site) so you can see the bug report tab. Also you will be able to see the Q&A section CM10.2 ATT thread, where you can ask questions
all questions should go to that section please
thanks
Data/WiFi working great (no lte here so can't test), messaging too, and whole ROM seems to be running very smoothly. Almost faster than stock I'd say and the phone seems to run at about the same temperature - though not as hot as usual when using a lot of data. Didn't encounter any unmentioned bugs and not had any crashes in my day of use, seems pretty stable. Nice job Lloir, honestly the only thing keeping me from using this is the call/audio issue. You've got an awesome start here, thanks for all the hard work!
guys please use the Q&A section or even the review tab (you need the XDA 2013 theme on)
thanks
Any update on the status? I'm itchy to try this out but would really like phone audio before I do.
loftwyr said:
Any update on the status? I'm itchy to try this out but would really like phone audio before I do.
Click to expand...
Click to collapse
Updates will be posted by the OP. FYI, that's a no no question too. Rest assured lloir is working on it unless otherwise stated by lloir.
Sent from my HTC One X+ using XDA Premium HD app
I'm currently running new builds, based on the AT&T X+ 4.2.2 leak
right now i'm updating lib's
Lloir said:
I'm currently running new builds, based on the AT&T X+ 4.2.2 leak
right now i'm updating lib's
Click to expand...
Click to collapse
is there a link to the leak??
TheJokah said:
is there a link to the leak??
Click to expand...
Click to collapse
if you can get access to my pc? sure, but i'm not going to be the target of a HTC c&d notice
short answer no.
Keep us updated. So excited!
later today, i will upload a build purely to see if people pre-4.2.2 can still flash + boot the rom with the old hboot...as i cannot use previous builds with the new 4.2.2 hboot
so yea....in a few hours check the downloads tab for a new download
Lloir said:
later today, i will upload a build purely to see if people pre-4.2.2 can still flash + boot the rom with the old hboot...as i cannot use previous builds with the new 4.2.2 hboot
so yea....in a few hours check the downloads tab for a new download
Click to expand...
Click to collapse
Still running Solomon's PA 4.2.2 build from Feb 19th. I'll assume I'm using the old hboot, then, so I'll try the build when it's posted!
Having a few issues with ril (data/gsm) at the moment, along with WIFI
the plus side looks like GPS is fixed, but can't confirm it 100%
more soon
don't go quoting this damned post here, but post in Q&A
Working as of now:
Camera
Video Camera
GPS (not sure if 100% yet)
GSM
Audio
Lights
Touch Screen
BT
MTP
Borked :
Not tested in call audio yet
WIFI (50% borked)
DATA (Kind of, doesn't connect to the interwebs)
SELinux (will be the last thing i fix)
Dialer app (phone.apk)
Thread Cleaned and Members please report vice posting against others, and I will ask any & all to watch their language, regarding profanity.
Thank You.

[DEV][trlte] Unified LineageOS device tree for Snapdragon Note4

I have the idea for an unified build from quite some time, but only now I'm trying to bring it to life.
Looking at LineageOS github and gerrit you can see that other devices (klte, m8) have the same stupid amount of variants, but they have merged them into one device repo.. So why can't this happen for the Note4?
Following their steps I've created an unified android_device_samsung_trlte (that includes SM-N910F/trltexx, SM-N910G/trltedt, SM-N910T/trltetmo, SM-N910W8/trltecan, SM-N910P/trltespr, SM-N910R4/trlteusc and SM-N910V/trltevzw), this proprietary_vendor_samsung and added this commit to the android_device_samsung_trlte-common that I'm currently using.
For now I'm able to use those repos to build a LineageOS-14.1 build that boots up, but w/o sim and camera being recognized.. For what I've tested (on trltexx) wifi and (strangely) bluetooth are working. Something is probably wrong with specific device blobs not being recognized/used properly.
It needs some work but I think this is a good base to start with.
trltexx/trltedt blobs are from here;
trltetmo/trltecan blobs are from here;
trltespr/trlteusc blobs are from here;
trltevzw is using trltespr blobs for now (there are no guaranteed working blobs repos for it at the moment, the only (WIP) way is to establish which are needed and extract them from hsbadr's builds).
The kernel is the same that I'm using for the not unified builds (android_kernel_samsung_trlte), at the moment testing if the klte's way of using the international variant defconfig works for us too.. other options are to add something like this commit to remove the need of a variant defconfig or merge the different defconfigs into one and use that instead.
Source:
unified_android_device_samsung_trlte
unified_android_device_samsung_trlte-common
unified_proprietary_vendor_samsung
android_kernel_samsung_trlte
I was going to share this anyway, but I'm sharing it now (even if there are still major problems) because I have a very limited free time where I can work on it, so, maybe, someone of you will join/fork/clone this project and help me out, finalizing it earlier and better (the support of experienced developers is needed and much appreciated).
I'm now going to mention the SeniorMembers/RecognizedContributors/RecognizedDevelopers that, maybe, have interest in this project.
@fattire @hsbadr @SaintZ93 @SferaDev @TheBr0ken @ZION959
If you get it to work, @_mone, I'll switch my daily builds to this unified one.
On a related matter, there seems to be a typo in the name of one of your repos: unified_andorid_device_samsung_trlte.
Let me also add @lilferraro to the list of devs, as I use his device tree to build for trltespr.
I built this and it boots, with the same issues you have (no SIM detected, camera is busted). Took a bunch of of logs. Getprop shows ro.build.fingerprint is trltetmo (which is right), ro.bootimage.build.fingerprint is trlte. Wifi and bluetooth are working. Mediaserver/libcameraservice service crashes repeatedly. I agree with you that having a unified tree for the entire Note 4 line is the way to go. I tried manually copying the blobs from /system/blobs/tmo/ to /system/lib and /system/vendor/lib but it didn't help.
what proprietary blobs did you use for sprint?
All device trees for the note 4 pie builds are up at
GitHub.com/tripLr-dev
User forum at Telegram
https://t.me/triplr_dev_users
Thanks to @_mone
And @ripee
I will do a test build of my Ubuntu Touch port using this unified repo and report back if anyone is interested. My port still needs a couple things to work but the stuff that works now should be enough to give me a good idea if it will work or not.
tigerpro357 said:
I will do a test build of my Ubuntu Touch port using this unified repo and report back if anyone is interested. My port still needs a couple things to work but the stuff that works now should be enough to give me a good idea if it will work or not.
Click to expand...
Click to collapse
Let us know what you need
Source code
GitHub.com/triplr-dev
Contact me on telegram t.me/telegram to get you in touch with testers and developers. .
I am EXTREMELY interested in a touch port.
Thanks
Also GitHub.com/underscoremone for all the older stuff
I actually have my work on github already, I am also on telegram in the ubports groups, and if you would like to help my repo is probably the best place to start (unless you prefer duplicating work) I only have sensors and the stylus left for hardware (both of which I have been trying to get working) the stylus is an issue on the ubports side but I dont understand the code enough for mir. I haven't had a chance to test the unified repo yet, but I will once I have a few minutes to actually do it.
I wonder how it work to create xda threads for Ubuntu touch, since they seem to have their own forums.
I think adding Ubuntu touch to xda would be an additional resource for users and developers.
tripLr said:
I wonder how it work to create xda threads for Ubuntu touch, since they seem to have their own forums.
I think adding Ubuntu touch to xda would be an additional resource for users and developers.
Click to expand...
Click to collapse
I agree, as all I really see on xda as far as Ubuntu Touch goes is prebuilt downloads which is good for letting people try it, but when I started I initially looked into xda but found no help. I do hope to see that change in the future though
Nice to see someone actually wanting to still develop for this device.. I love this Note4 still.
doubledragon5 said:
Nice to see someone actually wanting to still develop for this device.. I love this Note4 still.
Click to expand...
Click to collapse
Same here
We have several developers for note 4 snapdragon and exynos
T.me/triplr_dev_users
See you there
Roms
Tiny.cc/triplr
Tiny.cc/ripee
And many links in XDA for ROM threads
Post comments in XDA, and bug reports and logs in telegram
Android 10 in progress
Thanks @_mone
The lineage-17.1 thread is up!
[ROM][UNOFFICIAL][10] LineageOS 17.1 [tblte][trlte][trlteduos]
If you don't mind not having a working fingerprint sensor, or audio through the headphone jack, then Q is stable enough for daily use. As always when coming from an older rom version, it is highly recommended not to waste your time dirty flashing and just clean flash.
Q is still a work in progress, so I will still be releasing Pie builds, though maybe not as often. As in years past, once the Q bugs have been fixed up to the current Pie level, I will post about when my last Pie build will be. I will upload it to the Downloads tab located at the top of each page of this thread, and link it in the OP.

Call to test a Aspire Rom fix for Verizon users (n900v)

Dear Verizon users,
For the last two weeks me and @triskaw fixed the basic problems with our Aspire Rom to work on the Sprint network. Since both providers are CDMA based the fix should benefit Verizon users as well. To be sure of that I need beta testers. The following skills are mandatory:
1. Aspire rom user obviously
2. Know how to send logs
3. Use of telegram to communicate
If you fit that description please send me a PM. I have created a channel for testers and release fixes there.
AspireRom thread is here:
Aspire Rom V4.01 thread
Hope to see you soon in my new channel

General Incoming custom software that is NOT GSI

I just wanted to give you all a heads up that in my quest to fix up twrp/make custom ROMs, I've finally achieved a victory today after a couple weeks of effort. I have successfully compiled the N200 kernel from source. In the near future expect at least one custom kernel (likely to be caf upstreamed), and as of right now I am working on Lineage-18.1 bringup to start with then quickly move onto Android 12 custom ROMs long live the Nord n200!!
On a side note I could use some testers
Nord N200 Testers
Nord N200 Testers
A group for discussing N200 custom software testing. All off topic discussion has been moved to this group: https://t.me/+1qZHIItf9R80MTYx Check pinned messages for important messages and shared/confirmed working files.
t.me
Weird question but is it possible to add a wifi option to not broadcast ssid? Or is that not a kernel thing..
Also I can test but not until the end of next week
cass89 said:
Weird question but is it possible to add a wifi option to not broadcast ssid? Or is that not a kernel thing..
Also I can test but not until the end of next week
Click to expand...
Click to collapse
I'm not a kernel guru, It was luck that I got this kernel to compile lol.
But on a plus note, I did shim TWRP and managed to get it to mount the super.img so we will be able to flash gapps packages and magisk modules n stuff. I think I'm close to getting userdata decrypted as well
that group is very friendly and helpful, working towards development of this device
BTW, im Castiel in the TG

Categories

Resources