Code:
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*
*/
Hi,
here you can find my LineageOS 16.0 for the Samsung Galaxy Tab 4 7.0.
This ROM fits only for the SM-T235 and SM-T235Y, not for the SM-T230 and SM-T231 (different chipset).
At first I want to thank @spookcity138 for your work on the kminilte,
I've reused some things here from you.
For sure thanks to everyone else who ever worked on the Exynos3470.
Here you can see what's working / not working so far:
Spoiler: Whats working
Audio
Bluetooth
Boot
Cameras
Graphics
GPS, not sure if completely
Mobile data
OTA Updates
RIL
Sensor
Tethering via USB, WIFI and Bluetooth
USB
Video playback (HW/SW)
Wifi
Spoiler: Whats not working
Hardware overlay's, disabled by default
Spoiler: Links
TWRP
T235 / T235Y ROM
If you are going to use Gapps,
I recommend to use the pico package!
https://opengapps.org/
For the others, you can use microG if you want, I've enabled signature spoofing.
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my free time and it also costs a lot of money to buy hardware.
donate
Spoiler: Changelog
19.05.2021
20.05.2021
21.05.2021
24.07.2021
16.09.2021
17.09.2021
16.12.2021
10.01.2022
Spoiler: How to improve GPS
You could use a gps.conf from https://app.box.com/s/w57s1v1n3hie7l5lk28i for your location and replace /system/etc/gps.conf.
Or you try GPS Server Optimizer app for a faster 3D fix.
For both methods you need root rights.
Spoiler: How to install it?
Instructions
XDA:DevDB Information
[ROM][9.x][T235/T235Y][STABLE] LineageOS 16.0, ROM for the Samsung Galaxy Tab 4 7.0
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.3.0
Based On: LineageOS
Version Information
Status: Stable
Release Date: 2021-05-18
Created 2021-05-18
Last Updated 2022-01-10
*Reserved,
First builds are up.
I knew you would make it!
Will gladly try your ROM but i will have to wait untill the weekend..
prkfsz said:
Will gladly try your ROM but i will have to wait untill the weekend..
Click to expand...
Click to collapse
I'm testing it since yesterday and I have to say I'm really satisfied,
as soon as I have fixed the camera's, mobile data and the acceleration sensor, this ROM should be great.
html6405 said:
I'm testing it since yesterday and I have to say I'm really satisfied,
as soon as I have fixed the camera's, mobile data and the acceleration sensor, this ROM should be great.
Click to expand...
Click to collapse
Sounds good! Looking forward to try it out. And I hope there will be enough people left with these devices to be able to use your build.
Btw, did you have any use of the old marshmallow for it? Played a bit with it yesterday and it seems realy stable! The only thing that puts me off there is the small font.. There are of course ways to increase the size with some apps, but they are usually limited...
So, i hope there are usual ways to make the font bigger in your build for us elderly..
prkfsz said:
Btw, did you have any use of the old marshmallow for it?
Click to expand...
Click to collapse
Nope ,
never tried this, you can set the font size as it should be in LOS, just try it if it's big enough .
Update 19.05.2021:
Programmed new open source HAL for the acceleration sensor, screen rotation is working now.
Update 20.05.2021:
Fixed TWRP blank screen bug
Created thread for TWRP 3.5.2
Included swap memory
Fixed OTA function
Fixed camers's
Fixed mobile data
wow, it sounds you're pretty much done with it and got most, if not all of the things working?
Now i am really looking forward to the weekend to give it a go!
Just hope more and many people will find this..
prkfsz said:
wow, it sounds you're pretty much done with it and got most, if not all of the things working?
Click to expand...
Click to collapse
Yes all my issues after the first boot are resolved, now I have to test further and I will today,
maybe there will be an OTA update or not, we will see .
prkfsz said:
Just hope more and many people will find this..
Click to expand...
Click to collapse
I hope too, this device makes fun so far, small, but not too small, you can easily put it in your pocket .
Update 21.05.2021:
Fixed Bluetooth audio
Fixed Bluetooth voice call audio
Included an open source audio HAL and configured it for these devices, in future we won't need the old audio blob.
Temporarily disabled hw overlay's.
Update is via OTA available.
prkfsz said:
wow, it sounds you're pretty much done with it and got most, if not all of the things working?
Click to expand...
Click to collapse
Another day of work, it would have been too beautiful, if everything would be working .
Hi, where are the sources? In your github page, there aren't. I'm just curious to see what you have done, and in that way, I could fix something more in the other Tab 4 models that I maintain.
matteo0026 said:
Hi, where are the sources? In your github page, there aren't. I'm just curious to see what you have done, and in that way, I could fix something more in the other Tab 4 models that I maintain.
Click to expand...
Click to collapse
Just be patient, I will sync everything soon, I'm working simultaneously on more than 10 devices,
you will get them.
html6405 said:
Just be patient, I will sync everything soon, I'm working simultaneously on more than 10 devices,
you will get them.
Click to expand...
Click to collapse
Okay, thanks. When you'll push them, do with all the history too, please.
html6405 said:
Update 21.05.2021:
Fixed Bluetooth audio
Fixed Bluetooth voice call audio
Included an open source audio HAL and configured it for these devices, in future we won't need the old audio blob.
Temporarily disabled hw overlay's.
Update is via OTA available.
Click to expand...
Click to collapse
Managed install it finally! Have to give a tip to people that are going to do that - the latest TWRP can not mount the whole /data and format it if you have encryption. In that case you have to downgrade to the old 3.0.X TWRP first, and then go back to the latest TWRP to flash LOS16. Took me a while to find the solution for this
Writing this review on the t235, connected to a bt keyboard after the last OTA update..
Really good job! Everything seems to be working. And i can get bigger fonts! After the last update even bt works, which was important for me. The only bigger thing i haven't tested is mobile data.
And it's not that it's huge, but i am experiencing some microlags. Perhaps not surprising considering it's age and that it wasn't really a flagship device already when it was released..
Thank you for this! I will of course keep on testing for a while. And, just curious - will there be /e/?
prkfsz said:
Managed install it finally! Have to give a tip to people that are going to do that - the latest TWRP can not mount the whole /data and format it if you have encryption.
Click to expand...
Click to collapse
This is normal, but you should be able to wipe the whole data partition.
prkfsz said:
Perhaps not surprising considering it's age and that it wasn't really a flagship device already when it was released..
Click to expand...
Click to collapse
I'm actually surprised, that it run's as well as it's doing, it could be worse with this hardware .
prkfsz said:
And, just curious - will there be /e/?
Click to expand...
Click to collapse
If you're my only user, not , but everybody could use my sources and build /e/ out of it,
it actually should work out of the box.
Update 22.05.2021:
Fixed menu button configuration in settings
Made some RAM optimizations and tweaks
Made an Android go config
Removed unneeded button light and LED code, this device doesn't have any of them
Created many selinux labels, so we could switch it to enforcing in the future
Via OTA.
Hi
Thanks for keeping our device alive
I've lost hope long time ago.
Where can I download this? been trying to revive this device for the past few weeks and finally saw this today!!
Related
Code:
Code:
/*
* Your probably long expired warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
Please Note:I do not have a Verizon Fascinate!!!! The closest thing I have is a Telus Fascinate 4G, which is essentially a Galaxy S 4G. However, this ROM has been built for (and tested on) a Verizon Fascinate.
Installation Instructions - Thanks Ophidian_DarkCore!
Ophidian_DarkCore said:
Make sure to do the following before flashing this rom: flash this https://mega.nz/#!YBYXGTRI!7NscLqn139vvNCroS94HlQ6uNYpTFqmc1y3ktvtQIsw in odin https://drive.google.com/file/d/0B0J5C6YxKg67bW11WFJrbjYxNW8/view?pli=1
Gingerbread bootloader is required, you must have previously been on cm11 before using this rom, otherwise go to one of the cm11 threads and follow the 'from stock' instructions.
Click to expand...
Click to collapse
1. Read "Things to take note of" below
2. Wipe system, data, and cache paritions (just in case)
3. Install zip
4. If you want root (SuperSU) or Gapps, install them now (or later, if you so desire)
The first boot can take several minutes. Be patient. If it takes 10+ minutes, pull the battery and reboot to recovery.
Things to Take Note Of
The RIL (aka data, SMS, calls, etc) is NON-FUNCTIONAL.
Humberos (the i9000 maintainer) has moved on to different projects which means no first-gen Galaxy S devices are being actively maintained. Builds may break at any time!
Selinux is currently in permissive mode. I'm not sure whether or not it can be switched to enforcing without breaking things
The USB connection is MTP and not mass storage as Omni has removed mass storage. Unfortunately, it sometimes is super-duper slow. In recovery there is still an option to mount as mass storage device.
Live wallpapers are not present as this definitely qualifies as a low-ram device...
Tv-out support is not present. It was removed upstream and I don't want to bother adding it back in.
This build is very close to the official omni source code. This means that the recovery is TWRP and there aren't any added "features"
In order to get it rooted, you need to install SuperSu.
Gapps slow down the i9000 and Galaxy S 4G significantly so tread carefully.
Backup Backup Backup! I'm not responsible for you losing any data.
Working
It boots!
Wi-Fi
Seriously, I'm not exactly sure what else works. I suspect that most other functions including Bluetooth and auto-brightness work but I'm not sure
What doesn't
RIL, cause I removed it...
Some of the soft keys (possibly fixed in latest build)
You tell me...
Everything else is not tested!!!
XDA:DevDB Information
Unofficial OmniRom 5.1 for the Samsung Fascinate, ROM for the Samsung Fascinate
Contributors
xc-racer99, Ophidian_DarkCore, humberos
Source Code: https://github.com/omnirom
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: MTD Rom
Based On: OmniRom
Version Information
Status: Testing
Created 2015-08-01
Last Updated 2015-08-01
Thanks Time!
This would not have been possible without the following people:
Thanks to humberos for bringing Lollipop to the first-gen Galaxy S series. This would not have been possible without his work.
Thanks to Ophidian_DarkCore for being the primary tester and prompting me to work on this project.
Thanks to hhp_211 for doing some testing and offering to send me a Fascinate.
Thanks to all others that have helped get this phone to where it is today!
Thanks to vcmerritt. A name you're probably not familiar with, but he was the only one to create something for the T959P (my phone) and without him I'd still be on stock...
Build your own!
Follow the instructions at http://docs.omnirom.org/Setting_Up_A_Compile_Environment using the android-5.1 branch
Before doing a repo sync, put the galaxy_s_series.xml file from the Downloads folder in .repo/local_manifests folder of the source tree.
After syncing the source, open a terminal and in the directory where you downloaded the source code type "source ./build/envsetup.sh" and then "brunch fascinatemtd"
Changelog
Changelog for 2015/08/01 Build
Untested!!!!!
TWRP fix (I think)
Totally removed RIL, prior builds have RIL there but its non-functional
Changelog for 2015/08/13 Build
Untested!
Encryption should now work
Keymapping (ie soft keys Home and Back) may be fixed
Changelog for 2015/08/31
Updated Android version (5.1.1_r5 to 5.1.1_r12)(upstream Omni Change)
SoD should be fixed...
Untested by me
Source Code and Downloads
Main Source
http://github.com/omnirom
Device Specific Source Code
http://github.com/xc-racer99/android_device_samsung_fascinatemtd for the device tree (see android-5.1 branch)
http://github.com/xc-racer99/android_device_samsung_aries-common for the common device tree (see android-5.1 branch)
http://github.com/xc-racer99/android_kernel_samsung_aries for the kernel (see android-5.1 branch)
http://github.com/xc-racer99/proprietary_vendor_samsung for the prop blobs (see android-5.1 branch)
Downloads!
All builds are found at https://drive.google.com/folderview...VVSzJxYVU3eHlWZGR1VVNZUWk1V1QzOUk&usp=sharing
Gapps
Gapps can be installed from http://forum.xda-developers.com/showpost.php?p=59731008&postcount=2
SuperSu
SuperSu can be found at https://download.chainfire.eu/696/SuperSU/
Make sure to do the following before flashing this rom: flash this https://mega.nz/#!YBYXGTRI!7NscLqn139vvNCroS94HlQ6uNYpTFqmc1y3ktvtQIsw in odin https://drive.google.com/file/d/0B0J5C6YxKg67bW11WFJrbjYxNW8/view?usp=sharing
Gingerbread bootloader is required, you must have previously been on cm11 before using this rom, otherwise go to one of the cm11 threads and follow the 'from stock' instructions.
EDIT: recommended gapps https://basketbuild.com/devs/TKruzze/5.1.x GApps Packages/MODULAR - Pico GApps
Ophidian_DarkCore said:
Make sure to do the following before flashing this rom: flash this https://mega.nz/#!YBYXGTRI!7NscLqn139vvNCroS94HlQ6uNYpTFqmc1y3ktvtQIsw in odin https://drive.google.com/file/d/0B0J5C6YxKg67bW11WFJrbjYxNW8/view?usp=sharing
Gingerbread bootloader is required, you must have previously been on cm11 before using this rom, otherwise go to one of the cm11 threads and follow the 'from stock' instructions.
Click to expand...
Click to collapse
Thanks, I wasn't sure how you installed it. Will update OP.
xc-racer99 said:
Thanks, I wasn't sure how you installed it. Will update OP.
Click to expand...
Click to collapse
Ophidian_DarkCore said:
Make sure to do the following before flashing this rom: flash this https://mega.nz/#!YBYXGTRI!7NscLqn139vvNCroS94HlQ6uNYpTFqmc1y3ktvtQIsw in odin https://drive.google.com/file/d/0B0J5C6YxKg67bW11WFJrbjYxNW8/view?usp=sharing
Gingerbread bootloader is required, you must have previously been on cm11 before using this rom, otherwise go to one of the cm11 threads and follow the 'from stock' instructions.
EDIT: recommended gapps https://basketbuild.com/devs/TKruzze/5.1.x GApps Packages/MODULAR - Pico GApps
Click to expand...
Click to collapse
OK, Only worked from the odin cwm.
I tried flashing and while I got*cwm 6.0.5.1 and/or twrp,,, It looked like it installed cm11 and/or omni,,, but nothing ever booted, always looped back to recovery.
1st impressions are wow!!
looks good and kernel has OC
and a few nice features.
Good work on all involved!
Installed beta SuperSU-2.49
Gonna test with 200/1400, interactive(tweaked), deadline-1024, KSM-off, standard LMK. for now*
Stable so far.
I'll test changing vm heapsize and LMK values
Also trying omni switch, but probably go back to asop recents as its using a lot of mem
oh and I'll check Big Mem settings too.
So far no gapps installed yet but loaded up subway surfer and candy crush,,, both had significant lag before,,, on cm 11, du, slim before,,, but are running fantastic so far on omni !
Later:
Gapps : I went very minimal install package,
Yes performance still takes a hit and I've also noticed some random reboots too.
I'd like to go back and try again without a gapps to make sure/verify, but i don't remember any reboots without gapps.
As a side note,, I wish some one could build a modified base play services that didn't have all the extra services stuff like,,, in car, fit, nfc, weareable, etc.
I always disable that stuff even on my other/main phones.
.
i juse disableservice and autostarts for that stuff.
my experience has been this rom idles for several days and no crashes. i guess oc's but a last_kmsg would be nice. then have a logcat gathering while you try to recreate the crash. or gtfo?
i was surprised to have 1400. i could never get hummingbirdover 1300 on gb, and i overvolted the piss out of it. even my other hummingbird(sammy aviator).
EDIT: "interactive(tweaked)" hispeed_freq?
edit edit: ksm is optimized in this kernel, and row is best for our flash until fiops is added.
will new releases ?
Godlovskiy said:
will new releases ?
Click to expand...
Click to collapse
I'm working out lots of bugs and improving performance. Expect a much improved build soon.
Meanwhile, I'm gonna be jamming out on one of my test builds(24 bit audio anyone?) I figured out gcc 4.8. all i'm gonna say for now is it's a user build, debugging all disabled in the kernel, fiops is proposed, telephony all removed, art is set to fully optimize. a bunch of awesome sauce that I'm not gonna tell about just yet
***I'm working out lots of bugs and improving performance. Expect a much improved build soon.***
in buld 08/01 when I turn on OC phone don't wake
Godlovskiy said:
***I'm working out lots of bugs and improving performance. Expect a much improved build soon.***
in buld 08/01 when I turn on OC phone don't wake
Click to expand...
Click to collapse
OC is very phone specific. An OC that works on my phone may not work on your phone. That's one of the reasons the clock speed is normally only 1Ghz - all devices can support it. Some will definitely support higher (there were rumors of people going up to 1.8Ghz a few years back...). For me, 1.2Ghz is stable, 1.4Ghz often crashes.
If the phone isn't waking with an OC, you've pushed it too far. Try a lower OC.
Godlovskiy said:
will new releases ?
Click to expand...
Click to collapse
The only way I can do new releases is if somebody sends me bug reports. Since I don't have a fascinate, I can't see what problems will appear. Anything I find out that is wrong on my device (essentially a Galaxy S 4G) that is common with the Fascinate will come to the Fascinate but I haven't found anything like that since I put up the last build.
it is noteworthy that in build from 30/07 this is not observed
Godlovskiy said:
it is noteworthy that in build from 30/07 this is not observed
Click to expand...
Click to collapse
Ok, that is very noteworthy. I figured it was the same on all of them. Does it only not wake up when OC is enabled? I'll have a look through my code and see exactly what changed.
The most likely way to get around this, so to speak, would be to replace the boot.img in the new build with the one from the older build and then flash the zip. OC is mostly at the kernel level, so the boot.img should be the trick.
If someone does this and they don't see any adverse effects such as wakelocks, I'll do up a new build with the relevant change reverted.
Godlovskiy said:
it is noteworthy that in build from 30/07 this is not observed
Click to expand...
Click to collapse
OC didn't actually work in that build I think.
---------- Post added at 01:57 PM ---------- Previous post was at 01:55 PM ----------
xc-racer99 said:
Ok, that is very noteworthy. I figured it was the same on all of them. Does it only not wake up when OC is enabled? I'll have a look through my code and see exactly what changed.
The most likely way to get around this, so to speak, would be to replace the boot.img in the new build with the one from the older build and then flash the zip. OC is mostly at the kernel level, so the boot.img should be the trick.
If someone does this and they don't see any adverse effects such as wakelocks, I'll do up a new build with the relevant change reverted.
Click to expand...
Click to collapse
On 200 to 1.4 it stays on a black screen unless you fiddle with the volume buttons before waking the screen.
xc-racer99 said:
OC is very phone specific. An OC that works on my phone may not work on your phone. That's one of the reasons the clock speed is normally only 1Ghz - all devices can support it. Some will definitely support higher (there were rumors of people going up to 1.8Ghz a few years back...). For me, 1.2Ghz is stable, 1.4Ghz often crashes.
If the phone isn't waking with an OC, you've pushed it too far. Try a lower OC.
The only way I can do new releases is if somebody sends me bug reports. Since I don't have a fascinate, I can't see what problems will appear. Anything I find out that is wrong on my device (essentially a Galaxy S 4G) that is common with the Fascinate will come to the Fascinate but I haven't found anything like that since I put up the last build.
Click to expand...
Click to collapse
I can help you with bug reports,you just shoud tell me what I have to do
Cross09 said:
I can help you with bug reports,you just shoud tell me what I have to do
Click to expand...
Click to collapse
Awesome! Find what doesn't work, reproduce the issue, and then take logs as per http://forum.xda-developers.com/showthread.php?t=2185929 and then let me know. It helps if you explain in detail what exactly you do - more detail is always better than less. While this doesn't really apply here as there's not many builds, its always good to know if the bug is a regression (ie it worked in past builds but no longer works) or if it never worked in the first place.
To transmit this info you can use the bug reports tab at the top of this thread, PM, or just post in the main thread, it doesn't matter to me.
Cross09 said:
I can help you with bug reports,you just shoud tell me what I have to do
Click to expand...
Click to collapse
Here's something for you to do. When headphones are plugged in, no music is playing, and the screen is off, collect logs on why it won't come back on until the headphones are removed. Collect a logcat constantly throughout. Then grab a kmsg and dmesg after you remove the headphones and turn the screen back on.
Collect logs during listview scrolling.
Let me know if the play store can install apps.
Ophidian_DarkCore said:
I'm working out lots of bugs and improving performance. Expect a much improved build soon.
Meanwhile, I'm gonna be jamming out on one of my test builds(24 bit audio anyone?) I figured out gcc 4.8. all i'm gonna say for now is it's a user build, debugging all disabled in the kernel, fiops is proposed, telephony all removed, art is set to fully optimize. a bunch of awesome sauce that I'm not gonna tell about just yet
Click to expand...
Click to collapse
If you got 24 bit audio working, you would be my hero. I've been using this thing as a media player for a long time and it's fantastic, but I've been having some issues with Geewiz Media and this would be a nice improvement.
THANKS!
quickgiant said:
If you got 24 bit audio working, you would be my hero. I've been using this thing as a media player for a long time and it's fantastic, but I've been having some issues with Geewiz Media and this would be a nice improvement.
THANKS!
Click to expand...
Click to collapse
I also would be thankful if you would add 24 bit audio.
Thanks
xda_bg said:
I also would be thankful if you would add 24 bit audio.
Thanks
Click to expand...
Click to collapse
the frame size of 10 million exabytes is larger than my patience^2
http://i.imgur.com/eljXmhJ.png
Code:
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
What is AOSP?
AOSP is Android as Google publish without other modifications. More or less AOSP is the Nexus devices stock rom without gapps.
Anyway to get a working system I added some changes from CodeAurora Forum and CyanogenMod. I added also 3 non-AOSP features for a better user experience (Advanced Reboot, "Clear All" button in Recents and an option to delete screenshots from the notification area) and I'm NOT going to add something other.
Features
Pure AOSP
It's pure AOSP (based on Slim and CAF)
Downloads
Latest Build
GAPPS (Please use the Micro GAPPS Package that's the one working properly)
Link To Download Folder
How To Install
1. Place ROM & Gapps in your SD Card
2. Reboot in Recovery Mode
3. Wipe Data/Factory Reset
4. Wipe Dalvik cache
5. Install the ROM zip
6. Install the GAPPS zip
7. Reboot
8. Profit
P.S: Huge shout out to Team M8 for making this possible, without them i am nothing.
XDA:DevDB Information
AOSPB For Verizon G3, ROM for the Verizon LG G3
Contributors
amirfida, PunkUnity
Source Code: https://github.com/AOSPB
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: AOSP + CAF + Some stuff from Slim
Version Information
Status: Testing
Created 2016-03-09
Last Updated 2016-03-11
News: AOSPB haven't updated their code from past couple of days so i won't compile until they update their source. Cheers
This is mine thanks download now
Because this is AOSP will android pay work?
Okay, here's whats not quite working right now
CaptainElwood said:
Because this is AOSP will android pay work?
Click to expand...
Click to collapse
NFC is stuck and causes a wakelock, remove NFC's APK from /system/app, so no, Android Pay does not work
And Baseband is not detected, this is a common issue with newer ROMs on the VS985, ill hunt down CM's commits for this
Probably a gapps issue, but Google Play Services refuses to work for signing in at the first boot, looking for my old gapps now, ill edit this if it was indeed because of the March 10th Gapps
Otherwise, it runs smooth as butter, keep up the good work!
KShion619 said:
Okay, here's whats not quite working right now
NFC is stuck and causes a wakelock, remove NFC's APK from /system/app, so no, Android Pay does not work
And Baseband is not detected, this is a common issue with newer ROMs on the VS985, ill hunt down CM's commits for this
Probably a gapps issue, but Google Play Services refuses to work for signing in at the first boot, looking for my old gapps now, ill edit this if it was indeed because of the March 10th Gapps
Otherwise, it runs smooth as butter, keep up the good work!
Click to expand...
Click to collapse
if you do find that commit please let me know, ill soon upload a new build
amirfida said:
if you do find that commit please let me know, ill soon upload a new build
Click to expand...
Click to collapse
https://github.com/CyanogenMod/andr...mon/blob/cm-13.0/rootdir/etc/init.baseband.sh
I haven't seen your version of g3-common or anything but on most ROMs this winds up being what you need to do
As far as Gapps, it only happens when you install OpenGapps Stock builds, pico runs perfectly
as far as NFC, ill try replacing the apk for it and libs from CM or XenonHD and get those posted if they work
KShion619 said:
https://github.com/CyanogenMod/andr...mon/blob/cm-13.0/rootdir/etc/init.baseband.sh
I haven't seen your version of g3-common or anything but on most ROMs this winds up being what you need to do
As far as Gapps, it only happens when you install OpenGapps Stock builds, pico runs perfectly
as far as NFC, ill try replacing the apk for it and libs from CM or XenonHD and get those posted if they work
Click to expand...
Click to collapse
hey thanks for that i really appreciate it, will mention you in credits for sure
waiting for the workaround, i never really use NFC so never knew that its not working, really appreciate your hard work
Edit: My build uses CM device trees so the file is already the same one, i am testing new build will release it soon
Edit 2: New build has been uploaded compiled with Uber Toolchain
Just curious will Layers themes work on this?
AngryManMLS said:
Just curious will Layers themes work on this?
Click to expand...
Click to collapse
nope it won't... Sorry
amirfida said:
nope it won't... Sorry
Click to expand...
Click to collapse
Aw well. I'll check out this ROM regardless. Thanks for bringing this to our G3.
AngryManMLS said:
Aw well. I'll check out this ROM regardless. Thanks for bringing this to our G3.
Click to expand...
Click to collapse
You are welcome
Found some odd little issue on the Newest Build, unsure if this one applies to the previous, but the Ringer, regardless of what ringtone is set, does not ring, and Autobrightness does not work, so turning it off is the only way to set brightness, and because you're using CM device trees and kernels, you technically have the proper libs, unless those files are on CM's venders for LG :silly:
KShion619 said:
Found some odd little issue on the Newest Build, unsure if this one applies to the previous, but the Ringer, regardless of what ringtone is set, does not ring, and Autobrightness does not work, so turning it off is the only way to set brightness, and because you're using CM device trees and kernels, you technically have the proper libs, unless those files are on CM's venders for LG :silly:
Click to expand...
Click to collapse
Hey, thanks for pointing out those issues, yes i am using CM kernel and device trees i guess that's the reason brightness is not working properly because even CM had that issue many users reported that, i guess its fixed. Ill build again and see if these issues are fixed and if they are ill post the build. AOSPB guys haven't updated their source from past 17 Days that's the reason i didn't make a new build. Thanks once again
amirfida said:
Hey, thanks for pointing out those issues, yes i am using CM kernel and device trees i guess that's the reason brightness is not working properly because even CM had that issue many users reported that, i guess its fixed. Ill build again and see if these issues are fixed and if they are ill post the build. AOSPB guys haven't updated their source from past 17 Days that's the reason i didn't make a new build. Thanks once again
Click to expand...
Click to collapse
yeah, im mainly referring to the CM vendor trees, im not quite sure if that matters
AngryManMLS said:
Aw well. I'll check out this ROM regardless. Thanks for bringing this to our G3.
Click to expand...
Click to collapse
In 6.0 rro was merged. Any aosp or slim rom on 6.0 will work with layers as long as it doesnt have cmte.
NOTE: THERE'S A NEW THREAD HAS BEEN MADE. ANY UPDATES FROM THIS THREAD WILL BE MOVED TO THE NEW THREAD. THIS THREAD IS NOW CLOSED!!
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.1 (MM), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*
*/
BEFORE INSTALLING THIS ROM, MAKE SURE YOUR DEVICE MODEL IS THE SAME AS TITLE
IF YOU ASK ANY QUESTIONS LIKE "IS THIS FOR MODEL BLABLABLA" THEY WILL BE ALL IGNORGED
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.
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
And most important: DON'T READ THE OP
What's working:
RIL (Calls, SMS, Mobile data) [Dual-SIM]
Wifi (connection, tethering, etc)
Bluetooth
Camera, video codecs
Storage (both internal and external)
Storages (internal, external, adoptable storage) (*)
Offline charging
zRAM (compressed-RAM swap)
GAPPS
Tethering (USB, Wifi, Bluetooth)
GPS
Torch (flashlight)
WiFi-Direct
SELinux enforcing
New lz4 compressor/de-compressor for zram (new)
BUGS/Not working :
There're lots of bugs, but main are
No sound (beware making alarm while running this ROM), also Sound Recording doesn't work
Sound quality not too good when playing loud music or sound
FM radio app FC (due to missing libraries)
Screen recorder freeze the system (due to codecs, maybe)
Screen flickering on apps only (known as "strict mode"). Quick solution is pressing recents button, then return to the app. Currently, we can't disable it through Developer options
Distorting sound when using Bluetooth headset in call
WiFi-Direct does not work
WiFi auto-disconnect
AudioFX is not working
Battery drain caused by RIL
Cannot switch mobile data to other SIM without reboot
First time installing CyanogenMod 13 to your Galaxy V, or coming from another ROM:
Install TWRP Recovery
Reboot into Recovery using 3-button-combo (Vol-up+Home+Power)
Do a Nandroid backup! (Optional and only if you weren't running TouchWiz before)
WIPE (wipe data/factory reset + wipe cache partition + format /system partition)*
Install the ROM from sdcard using TWRP Recovery
Optionally install the Google Apps ( get it here: https://opengapps.org ) (pico GAPPS recommended) (*)
(*) NOTE: If you're about going to install GAPPS with ROM, install it right after you've installed the ROM, else you have to do a factory reset if you've booted the ROM first
DEAR KANGERS
Click to expand...
Click to collapse
If you're going to reuse our work, be kind 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"
DOWNLOADS:
Click to expand...
Click to collapse
ALPHA-1: Link
BETA-1: Link
BETA-1Update1: XDA MF
BETA-2: XDA MF
BETA-3:
ROM XDA MF
BOOT.IMG XDA MF
BETA-4: Mirror MF
Want some screenshots? Get them in Screenshot tab above
XDA:DevDB Information
CyanogenMod 13, ROM for the Samsung Galaxy Ace 4
Contributors
doesntexits, ngoquang2708
Source Code: https://github.com/ngoquang2708/android_device_samsung_vivalto3gvn/tree/cm-13.0
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock 4.4.2
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: 3
Beta Release Date: 2016-08-01
Created 2016-06-14
Last Updated 2016-08-28
CHANGELOG
ALPHA-1
Initial release
BETA-1
Fixed RIL, switched to beta builds
Switched to AOSP charging module
Fixed screen flickering
Fixed audio (thanks to @ngoquang2708)
BETA-2
Fixed screen flickering.
Fixed audio, now you can maximize your volume!
BETA-3
Fixed AudioFX
Fixed WiFi auto-disconnect
Working WiFi-Direct
No more "lock" at Setup Wizard
SELinux is now in Enforcing mode
BETA-4: Post #199
F.A.Q
Q: ROM startup too slow?
A: This device is just a single-core phone, so the first startup is super-duper slow, and some lags are expected during usage
Q: ETAs?
A: See here: Link
Q: Anymore models supported?
A: SM-G313ML, SM-G313H
Q: Is init.d supported on this ROM?
A: Every CyanogenMod ROMs support init.d, so be free at scriptings
Q: Can you include ABCXYZ feature / Samsung Apps here?
A: NO!
Q: Can i use your ROM as a base for portings?
A: Yes, you could, but give proper credits
Q: Status 7 when installing the ROM?
A: Use TWRP recovery to install the ROM, as CWM is not supported yet
Q: Server error in Google Play Store?
A: Install latest Google Play Services manually first (might take long time, due to Lollipop's nature), then you can install apps from GG Play as usual
Q: How to use adoptable storage feature? I see it's new in Marshmallow
A: Go to Settings >> Storage & USB >> Tap on the SD card label (not the eject icon) >> 3 dots menu on the top right >> Settings >> Format as internal and done!
Q: Where's the MTP option in Marshmallow? I don't see it in Storage settings
A: This feature has been moved to Developer settings, and will reset to default (Charging) after every reboots. Enable developer options first by tapping 7 times on Build number in About phone section >> Go to Developer settings >> Select USB configuration. The fastest way to do this is plug in your USB with your PC, scroll down notification bar and tap on "USB for Charging"
Q: Where's the "running" section in Apps settings?
A: It has been cut off separately to Memory setting and "Running services" in Developer settings. You can see the memory used by apps for a period of time and closing apps too, but they won't disappear in the menu, and in "Running services", still same as old-fashioned running apps section
@adriansticoid
Your guessing is right. Here's our surprise
doesntexits said:
@adriansticoid
Your guessing is right. Here's our surprise
Click to expand...
Click to collapse
Thank you so much for this! Much appreciated. But I see that it is not suitable yet for daily use. Gonna wait until the camera and RIL bigs are fixed then I'll immediately switch to this.
Sent from my SM-T110 using XDA Labs
adriansticoid said:
Thank you so much for this! Much appreciated. But I see that it is not suitable yet for daily use. Gonna wait until the camera and RIL bigs are fixed then I'll immediately switch to this.
Sent from my SM-T110 using XDA Labs
Click to expand...
Click to collapse
Actually, the camera is usable, but sometimes during capture only, it lags (just for minimal duration, count by miliseconds). Video recording works just fine, but no sound
When RIL is fixed, we'll switch the ROM to beta builds, as it's a major issue for now
doesntexits said:
Actually, the camera is usable, but sometimes during capture only, it lags (just for minimal duration, count by miliseconds). Video recording works just fine, but no sound
When RIL is fixed, we'll switch the ROM to beta builds, as it's a major issue for now
Click to expand...
Click to collapse
Oh yeah one more thing. That sound bug. That one along with the RIL bug are the majors for now. Really man if you are just near I'll invite you to my house to have some snacks here. I hope hose are fixed soon.
Sent from my SM-T110 using XDA Labs
adriansticoid said:
Oh yeah one more thing. That sound bug. That one along with the RIL bug are the majors for now. Really man if you are just near I'll invite you to my house to have some snacks here. I hope hose are fixed soon.
Sent from my SM-T110 using XDA Labs
Click to expand...
Click to collapse
OK thanks, but I want my money back, as I've lost all of them to buy a new phone due to a funny reason: Don't know where I've kept them
Also because of that, I've a reason to have more time developing for Galaxy V, else I would doing for both phones
doesntexits said:
OK thanks, but I want my money back, as I've lost all of them to buy a new phone due to a funny reason: Don't know where I've kept them
Also because of that, I've a reason to have more time developing for Galaxy V, else I would doing for both phones
Click to expand...
Click to collapse
If only I can spare some, but I am only a student. Haha.
Sent from my SM-T110 using XDA Labs
Guys, I found our old running apps menu
It was in Developer options >> Running services
cmn guys, make this for sm-g313hu
gsrq said:
cmn guys, make this for sm-g313hu
Click to expand...
Click to collapse
Sorry, we don't have it
Btw, you've CM12.1 already right? Just use it
Fun fact: 6 months ago, I was acting like you too
This is great but, cm12 is still better for now Im excited for the final release. Im still waiting for your cm11 3rd final release.
Mc Code said:
This is great but, cm12 is still better for now Im excited for the final release. Im still waiting for your cm11 3rd final release.
Click to expand...
Click to collapse
Don't wait for that release. It's EOL (end-of-life) now
doesntexits said:
Don't wait for that release. It's EOL (end-of-life) now
Click to expand...
Click to collapse
What does that actually mean?
Sent from my SM-T110 using XDA Labs
adriansticoid said:
What does that actually mean?
Sent from my SM-T110 using XDA Labs
Click to expand...
Click to collapse
It means CM11 won't be having future builds anymore
doesntexits said:
It means CM11 won't be having future builds anymore
Click to expand...
Click to collapse
I see. CM11 is pretty stable now. CM13 should be more focused on.
Sent from my SM-T110 using XDA Labs
Great news guys! We have been working hard, and.... RIL now fixed!
We can make calls, send SMS, using mobile data for sure. Although that, we still having a great trouble: SystemUI and Phone FC
When that problem is fixed, we'll release BETA-1 for sure
Fun fact: Audio is dead, but we can still hear what people are saying in calls
I am confuse, that how can you upgrade your kernel.
Your device Kernel version was 3.10.17 and now its upgraded to 3.10.34
How is that possible.
I planned to port this ROM to higgs2g if the CM13 build process always fails.. Can I have permission to port this ROM? Thanks in advance
Sent from my higgs2g using XDA Labs
What is it
It is an under developpement LineageOS 14.1 build from random picked sources official LineageOS sources devices trees, and sonyxperiadev kernel. No modification into the code except to get device working. This rom is not intended to be used as daily usages, it is under development! The bigest part of this dev is done by the sonyxperiadev developers/contributors. The idea is to share this built with the community is to improve this rom (and the mentioned sources) faster to maybe, someday, get official again for our D6603. And maybe real dev can help It is an stable version of CyanogenMod 12.1 build from official CyanogenMod trees, and original kernel upgraded to include security patches. No modification into the code except kernel. As CyanogeMod doesn't exist anymore and android L is the only valuable (for now) custom rom for our devices, the idea is to provide upgrade of the original rom without modification. For now only kernel is upgraded, any help to backport AOSP security patch into gerrit is welcome
Disclaimer
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 me for messing up your device, I will laugh at you.
*
*/
Who can use it
it is only for z3(c) and unlocked upgraded bootloaders
This thread is intended to be used by everyone, devs and users
Prerequisites
Optional but highly recommend to upgrade your bootloader before, in case something goes wrong.
a twrp in the FOTAKernel/recovery partition
wipe data/cache (without wipe /data/media) in twrp (except coming from cm-12.x/13.x, upgrade should work)
Sources
Build instructions.
Kernel.
How to install
Install instructions
XDA:DevDB Information
CyanogenMod-12.1, ROM for the Sony Xperia Z3
Contributors
nailyk, derf elot
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Stable
Stable Release Date: 2017-02-14
Created 2017-02-16
Last Updated 2017-07-16
Releases
2017-07-16
z3 / md5: f70ad844e3bc235867611f005d72c6cc / sha1: 2088d8e4fe537cece6874306b3d3e3278225cb0f
2017-03-31
z3 / md5: e01c098ada5e7da0991eec39f0f4a6a7
z3c / md5: 36de84a26e46e6961a408a64769bfc01
2017-02-13
z3 / md5: ea6077dbf6bba6f3c318deea7e2cf335
z3c / md5: bd6b1ffbfa9e05e0a4fb2ac0220cb969
Reserved
First! Its good to see updated rom. Thank you zombie
ilqar.ehlimanov said:
okey my frend soryy :{
Click to expand...
Click to collapse
ilqar.ehlimanov said:
z3 dual d6633 ? :{
Click to expand...
Click to collapse
If you take 10 min to read threads instead of spamming them you will know I'm already working on it with @jonathan.lube (between your spams btw)
Edit: reported
Hi nailyk ... what security patch base is it ??? I'm on the last original CyanogenMod 12.1 nightly from october 2016 ... Are there any
changes or improvements in this build ???
Much greets and respect to your work ....
VivaLaBamm said:
Hi nailyk ... what security patch base is it ??? I'm on the last original CyanogenMod 12.1 nightly from october 2016 ... Are there any
changes or improvements in this build ???
Much greets and respect to your work ....
Click to expand...
Click to collapse
Thanks
@tomascus made kernel upgrades and I do not have the exact list.
This kernel is selinux upgraded to provide mush more compatibility with FOTAKernel recoveries, and some critical android security bulletins fix are included too.
However CM-12.1 is no more updated so any changes on this way.
So the only changes, compared to the last october official release, are available on the github. The build script is here, the only patch applied is the cm-12.1 defconfig.
I hope someone will help me to backport the security changes into CM to provide a full security updated rom.
Cm 12 is very stable the camera works. I noticed that also NFS No limits runs much better in cm12 I do not know if it was the ROM or some update just know that this incredible now
I have been using for a few days and I'm impressed with its performance. I know benchmarks don't mean a lot, but in real usage the feelings are as great as number suggest
Battery life is as good as stock (at least) and there are no real bugs. Only camera quality is worse than stock. I only miss a few options like network speed and others available on ExistenZ or Carbon, but this is going to be my daily driver for a long time!
Sent from my Xperia Z3 using Tapatalk
It was too good to be true xD. I'm having problems with GPS. There is a clear sky but the phone doesn't find any single satellite. I've attached logcat and dmesg. I hope it's not hardware related... http://cloud.tapatalk.com/s/58a8acfdebc71/Log-2017-02-18-09.23.30.csv.txt
http://cloud.tapatalk.com/s/58a8ad12e3415/Log_2017-02-18_21-22-31.txt
Sent from my Xperia Z3 using Tapatalk
F2FS Support?
Dinkec27 said:
F2FS Support?
Click to expand...
Click to collapse
Yes this rom have f2fs support (with encryption)
blackhawk_LA said:
It was too good to be true xD. I'm having problems with GPS. There is a clear sky but the phone doesn't find any single satellite. I've attached logcat and dmesg. I hope it's not hardware related... http://cloud.tapatalk.com/s/58a8acfdebc71/Log-2017-02-18-09.23.30.csv.txt
http://cloud.tapatalk.com/s/58a8ad12e3415/Log_2017-02-18_21-22-31.txt
Click to expand...
Click to collapse
Weird. I test gps and with satstat it works fine (indoor, in front of the window, like 3 min to get a fix).
I will take a look at your logs asap.
blackhawk_LA said:
I....Only camera quality is worse than stock...
Sent from my Xperia Z3 using Tapatalk
Click to expand...
Click to collapse
You meant fish eye bug and poorer quality then proprietary sony?
mathorv said:
You meant fish eye bug and poorer quality then proprietary sony?
Click to expand...
Click to collapse
Exactly. But for me it's still usable
Sent from my Xperia Z3 using Tapatalk
blackhawk_LA said:
Exactly. But for me it's still usable
Sent from my Xperia Z3 using Tapatalk
Click to expand...
Click to collapse
It's the original quality of lenses without any Sony makeup (drm).
Both indoor and outdoor pictures are bad, but indoor pictures are worse.
My NFC is not working... when i try to turn on the NFC it immediately turns off weird enough. don t know why. maybe you can help?
nailyk said:
Yes this rom have f2fs support (with encryption)
Weird. I test gps and with satstat it works fine (indoor, in front of the window, like 3 min to get a fix).
I will take a look at your logs asap.
Click to expand...
Click to collapse
Strangely today I tried and gps is now working perfectly without any change. When I tested the other day O waited for several minutes with clear sky and it was 0/0 Today I got around ten fixes and 21 satellites.
Sent from my Xperia Z3 using Tapatalk
pausyworld said:
My NFC is not working... when i try to turn on the NFC it immediately turns off weird enough. don t know why. maybe you can help?
Click to expand...
Click to collapse
Weird, indeed.
Can you please take a logcat? Maybe something obvious like a missing file.
Also do you replaced your back cover?
blackhawk_LA said:
Strangely today I tried and gps is now working perfectly without any change. When I tested the other day O waited for several minutes with clear sky and it was 0/0 Today I got around ten fixes and 21 satellites.
Click to expand...
Click to collapse
Glad it works again.
mmh sorry i don t know so much about that stuff. what you mean with back cover? like a normal cover for the phone? then no! i don t use one.
and how do i get a logcat?
pausyworld said:
mmh sorry i don t know so much about that stuff. what you mean with back cover? like a normal cover for the phone? then no! i don t use one.
and how do i get a logcat?
Click to expand...
Click to collapse
You can use this app https://play.google.com/store/apps/details?id=scd.lcex
Sent from my Xperia Z3 using Tapatalk
Liquid Remix
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. Hard & a lot.
*
*/
Gapps: Arm64 9
Magisk: current version
Downloads:
SM-T820
Previous Builds:
SM-T820
Sources:
https://github.com/srgrusso/manifests/tree/gts3l-liquid-10.x
I would like to give a huge thanks to @Valera1978 for building the sources and his continuing work on this device.
Changelog
T820
Notes
I'm looking for someone willing to test for the SM-T825
Known issues:
Camera is slow switching between back and front cameras.
Unable to register a fingerprint.
Perfect! Thanks for your work and for posting / uploading the manifest. I'll give it a go (soonish). (T820)
srgrusso said:
Notes
I'm looking for someone willing to test for the SM-T825
Known issues:
Camera is slow switching between back and front cameras.
Unable to register a fingerprint.
Click to expand...
Click to collapse
Can I flash the system on SM-T825
(don't will have kernel issues?)
Is Spen working, ignoring finger touches while in use?
The Creek 276 said:
Can I flash the system on SM-T825
(don't will have kernel issues?)
Click to expand...
Click to collapse
I need to do a special build for the T825. I will let you know when I have it built. If you're interested let me know.
hipocrazy said:
Is Spen working, ignoring finger touches while in use?
Click to expand...
Click to collapse
I don't know. I didn't have a spen. Maybe someone else can let you know. I would imagine it has the same issues as the other Roms for this device.
srgrusso said:
I don't know. I didn't have a spen. Maybe someone else can let you know. I would imagine it has the same issues as the other Roms for this device.
Click to expand...
Click to collapse
Could you please check whether it is possible to integrate the s-pen palm rejection feature?
This would make your rom really stand out against the others
It’s the one feature that let’s me stay on official firmware, although its soooo slow
srgrusso said:
I don't know. I didn't have a spen. Maybe someone else can let you know. I would imagine it has the same issues as the other Roms for this device.
Click to expand...
Click to collapse
Guancho said:
Could you please check whether it is possible to integrate the s-pen palm rejection feature?
This would make your rom really stand out against the others
It’s the one feature that let’s me stay on official firmware, although its soooo slow
Click to expand...
Click to collapse
Same here, please try to include this feature. :fingers-crossed:
Stogie87 said:
Same here, please try to include this feature. :fingers-crossed:
Click to expand...
Click to collapse
same here (lol)
if theres a chance of fixing the palm rejection problem i am willing to help you testing (i have a t825)
and i would even pay you 5 coffee if you made it .. the stock is so slow in comparison...
Hello There. I have downloaded and installed this ROM with BitGapps (as OpenGapps doesn't wanna download) and let me tell you, it's very unstable. As soon as I rebooted after installing this ROM, it was very slow. And BTW for me the S-Pen has the same problem as the Lineage OS one. The UI was Sluggish, and would hang a lot. And when I installed Magisk and installed V4A it would only reboot once I gave the password. It is in that loop since. The camera also crashes and so does the Fingerprint. Very Sad to say that I had to go back to The Tweaked Stock ROM.
Sent from SM-T820 using a pair of hands and a brain.
666anoymous666 said:
Hello There. I have downloaded and installed this ROM with BitGapps (as OpenGapps doesn't wanna download) and let me tell you, it's very unstable. As soon as I rebooted after installing this ROM, it was very slow. And BTW for me the S-Pen has the same problem as the Lineage OS one. The UI was Sluggish, and would hang a lot. And when I installed Magisk and installed V4A it would only reboot once I gave the password. It is in that loop since. The camera also crashes and so does the Fingerprint. Very Sad to say that I had to go back to The Tweaked Stock ROM.
Sent from SM-T820 using a pair of hands and a brain.
Click to expand...
Click to collapse
Did you do a wipe and format data before you flashed? Also did you try using open gapps?
srgrusso said:
Did you do a wipe and format data before you flashed? Also did you try using open gapps?
Click to expand...
Click to collapse
I had formatted everything before install and I can't download OpenGapps for some reason
Any Hope of reviving this? It has potential.
How stable was it? I can compile it based on the latest sources since there was a manifest
i installed it with magisk & without gapps
it worked fine i use it only with youtube vanced ...lasted 14hrs on single charge
defiantly better than stock
thanx
srgrusso said:
Notes
I'm looking for someone willing to test for the SM-T825
Known issues:
Camera is slow switching between back and front cameras.
Unable to register a fingerprint.
Click to expand...
Click to collapse
hi
i'm in if you need a tester
srgrusso said:
Changelog
T820
Click to expand...
Click to collapse
Hey man, I had a query. The manifest you have in your tree, it says that its based on a branch from a device called gtaXL (most probably a Tab A). So did you port the tree from that device or make one using Valera's Tree? Because if yes, we have access to Android 11 for this tab (which is AMAZING)