Database Info

[FIX] Android 4.2.x 4.3.x Google Maps 7 glitch

Hey there guys,
I found these drivers http://forum.xda-developers.com/showthread.php?t=2238348, but they are not suitable ATM.
Sorry for making you all happy with something that doesn't work. Let's make a good discussion about how we can instead make all this work.

steyn_e said:
Hey there guys,
I found these drivers http://forum.xda-developers.com/showthread.php?t=2238348 for our Sensations, which solves the graphical glitches in Google Maps 7. Please all use these in your ROM's. I also found an even newer version, but that is not compatible with the Linux kernel we are currently using (3.0.x).
The build number for these are [JB_VANILLA.04.02.02.060.053]. These need a 3.4.x kernel.
I hope you can all enjoy these! The package can be downloaded here.
You can simply be flash it through 4ext, afterwards clear dalvik+cache.
Have fun!
Click to expand...
Click to collapse
If they need a 3.4.x kernel you need to state clearly that they are for JB sense. None of the aosp jb roms here use a 3.4.x kernel.

sjknight413 said:
If they need a 3.4.x kernel you need to state clearly that they are for JB sense. None of the aosp jb roms here use a 3.4.x kernel.
Click to expand...
Click to collapse
Only the latter ones (which I didn't include a link for) are for 3.4.x. The ones linked work for 3.0.x, and I am using them now on CM10.2. They will also work on CM10.1, and maybe on CM10 if the kernel is 3.0.x or over. I'll try to find a link for the other ones for people using a Sense based ROM.

Okay, I made myself clear. The first download is for kernel 3.0.x (tested on CM10.2 and working), the second download is for kernel 3.4.x (and maybe further), but I cannot test that as I am not using a Sense based ROM. It is sourced directly from Qualcomm.
Now I'm thinking of it: we should probably make a list of compatible kernels for the different drivers. I'm using the Albinoman 3.0.100 kernel.

Sad to say, but I've still got glitches.. Installed with 4Ext and wiped cache + dalvik cache.
Albinoman's 4.3.1 26-10 with his kernel.

84Guzz said:
Sad to say, but I've still got glitches.. Installed with 4Ext and wiped cache + dalvik cache.
Albinoman's 4.3.1 26-10 with his kernel.
Click to expand...
Click to collapse
You did install the upper one? Which version of Maps are you using?
Also, what is the Linux kernel version of your rom (in device info)?
Let's make this work...

steyn_e said:
You did install the upper one? Which version of Maps are you using?
Also, what is the Linux kernel version of your rom (in device info)?
Let's make this work...
Click to expand...
Click to collapse
Yes, I got the one for a 3.0 kernel
Maps: 7.3.0
Kernel version: 3.0.100
The glitches are not as bad as they used to be, but try drawing the notification bar. Also the dialog to turn on GPS when starting navigation will flicker.
Edit: Press the "go to my location" button (top right) it will prompt a dialog to turn on GPS, which will flicker between opaque and transparent

84Guzz said:
Yes, I got the one for a 3.0 kernel
Maps: 7.3.0
Kernel version: 3.0.100
The glitches are not as bad as they used to be, but try drawing the notification bar. Also the dialog to turn on GPS when starting navigation will flicker.
Edit: Press the "go to my location" button (top right) it will prompt a dialog to turn on GPS, which will flicker between opaque and transparent
Click to expand...
Click to collapse
Tried it. It does the same with me once, but the second time it didn't. And just moving through maps doesn't glitch anymore.

steyn_e said:
Tried it. It does the same with me once, but the second time it didn't. And just moving through maps doesn't glitch anymore.
Click to expand...
Click to collapse
Do you mean you tried the notification bar? This keeps glitching with me.
Moving trough maps is OK indeed.

I've now modded the 2nd set of drivers to install on my device, let's see how this goes.

A few things:
1. These libs don't boot. If they "booted" for you then that's because the installer never installed them. The line in the updater script to mount /system makes it try and mount system as a yaffs2 partition, but we don't use yaffs2 we use ext4, so /system is never actually mounted. I modified the installer so it actually installs the libs and they do not boot. Some more proof of this is that the zip flashes very quickly, when it should actually take about 10-15 seconds to flash. They probably require a kernel with ION and a GPU driver from a 3.4 kernel.
2. Our Maps glitches are not being caused by our Adreno libs. Read my post HERE
3. The package for 3.4 kernels is not a flashable zip.
4. The package for 3.4 kernels does not necessarily require a 3.4 kernel (I have booted them on a 3.0 kernel); all they require is a kernel with a GPU driver from a 3.4 kernel and ION.

android1234567 said:
A few things:
1. These libs don't boot. If they "booted" for you then that's because the installer never installed them. The line in the updater script to mount /system makes it try and mount system as a yaffs2 partition, but we don't use yaffs2 we use ext4, so /system is never actually mounted. I modified the installer so it actually installs the libs and they do not boot. Some more proof of this is that the zip flashes very quickly, when it should actually take about 10-15 seconds to flash. They probably require a kernel with ION and a GPU driver from a 3.4 kernel.
2. Our Maps glitches are not being caused by our Adreno libs. Read my post HERE
3. The package for 3.4 kernels is not a flashable zip.
4. The package for 3.4 kernels does not necessarily require a 3.4 kernel (I have booted them on a 3.0 kernel); all they require is a kernel with a GPU driver from a 3.4 kernel and ION.
Click to expand...
Click to collapse
Yes, I've noticed the META-INF was missing in the 2nd one. However, it did do something. Maps is not even nearly as glitchy as it was. It only glitches now if something pops in front (like that "do you want to enable GPS" or the notification bar).
Our Adreno drivers want ION, and the camera wants PMEM, however is it even close to possible to make the camera libs work with ION?

steyn_e said:
Yes, I've noticed the META-INF was missing in the 2nd one. However, it did do something. Maps is not even nearly as glitchy as it was. It only glitches now if something pops in front (like that "do you want to enable GPS" or the notification bar).
As it is nearly impossible to rewrite the Adreno libs to use PMEM, is it even close to possible to make the camera libs work with ION?
Click to expand...
Click to collapse
Sebastian modified VilleC2 camera libs to work with our camera sensor and rewrote the camera driver, but Sebastian is on a whole different level from me
Also, the first package did absolutely nothing. I tested it and nothing was flashed to /system because the installer couldn't mount /system (because it's trying to mount /system as yaffs2). My Adreno version did not change, and when I fixed the package to install correctly, my phone did not boot (as they probably require ION and a 3.4 GPU driver; my kernel has a 3.4 GPU driver but ION is still necessary to get them booting). There's no such thing as in between with these Maps glitches; the glitches are either there or they're not.

android1234567 said:
Sebastian modified VilleC2 camera libs to work with our camera sensor and rewrote the camera driver, but Sebastian is on a whole different level from me
Also, the first package did absolutely nothing. I tested it and nothing was flashed to /system because the installer couldn't mount /system (because it's trying to mount /system as yaffs2). My Adreno version did not change, and when I fixed the package to install correctly, my phone did not boot (as they probably require ION and a 3.4 GPU driver; my kernel has a 3.4 GPU driver but ION is still necessary to get them booting). There's no such thing as in between with these Maps glitches; the glitches are either there or they're not.
Click to expand...
Click to collapse
So I've noticed. Isn't Sebastian's kernel ION?

steyn_e said:
So I've noticed. Isn't Sebastian's kernel ION?
Click to expand...
Click to collapse
Yes. Sebastian's kernel satisfies all the requirements to use these libs (ION and 3.4 GPU driver) so they should boot on any ROM using his kernel.

android1234567 said:
Yes. Sebastian's kernel satisfies all the requirements to use these libs (ION and 3.4 GPU driver) so they should boot on any ROM using his kernel.
Click to expand...
Click to collapse
Now the final thing is obviously to make that kernel work with your ROM. Possible at all?

steyn_e said:
Now the final thing is obviously to make that kernel work with your ROM. Possible at all?
Click to expand...
Click to collapse
Even if I managed to get all the basic things working (which I don't think I can do), getting the camera working would be a problem and we'd probably be forced to use PMEM on the whole kernel (which would defeat the purpose of a 3.4 kernel).

android1234567 said:
Even if I managed to get all the basic things working (which I don't think I can do), getting the camera working would be a problem and we'd probably be forced to use PMEM on the whole kernel (which would defeat the purpose of a 3.4 kernel).
Click to expand...
Click to collapse
That means there is no hope for getting every single thing to work on our phones?

steyn_e said:
That means there is no hope for getting every single thing to work on our phones?
Click to expand...
Click to collapse
Man, we are running android 4.3 on phone which was officialy updated to 4.0 only. That is normal that some thing arent working
Wysłane z mojego HTC Sensation przy użyciu Tapatalk 4

szotaa said:
Man, we are running android 4.3 on phone which was officialy updated to 4.0 only. That is normal that some thing arent working
Wysłane z mojego HTC Sensation przy użyciu Tapatalk 4
Click to expand...
Click to collapse
That doesn't mean we shouldn't try. I'd love to learn more about this stuff. And if someone can teach me, we Sensation users will have another driven Devver. I won't be able to do this on my own however, as it has been too long since I've last been devving for a Phone (that was my Touch Pro 2).

[EOL] [ROM] WIP CM12.1 [LMY49J] for ZTE Blade S6 (P839F30) - development thread

This development has come to a stop!
But further development is taken here.
Many thanks.
Hello everyone,
I start this thread to get some more development going on for the ZTE Blade S6.
It should encouraged others to join in or describing their own rom development for this device.
To start with I will show you my first alpha build, which means that most basic function should work now, of Cyanogenmod 12.1 for the Blade S6 (P839F30). I have the AS-Version of the device so be careful, if you have a EU Blade S6 or some other similar device. But at always be careful with your device, because I'm not responsible what you do with it, make a backup with TWRP before flashing the rom.
Things I tried:
called my phone
mobile Internet
wifi shows access Points
sound
button lights
camera working
breathing notification
Not Working:
Flash don't work when taking pictures.
UMS is not working correct
Preparation:
download unofficial CM12.1 and put it on your external sd Card
make a twrp backup
factory reset your device
optional - install this mod
install CM12.1
optional - install other region kernel - AU, EU
optional - install gapps
Credits:
Whole team of CyanogenMod https://github.com/CyanogenMod/android
lonespeaker for helping getting things started
KonstaT for TWRP
repos from piccolo-dev team, at which my work is based on.
Kernel Sources my own kernel repo
Kernel Sources ZTE
Please note this is the first time I do this, I'm still learning while doing and also some things I don't know.
Download Google drive
Updated Version 16.11.2016 using data/media as internal storage
Download links for the different kernels:
EU Version
AU Version
Previous Version 20.06.2016
10.02.2016

Concerning the wifi issue you could try the wifi zip file from fortek..see https://mega.nz/#F!c9AyURra!H4Oew0HB6JmqfPpmQ4SJqA

Something new here ??

slawoko said:
Concerning the wifi issue you could try the wifi zip file from fortek..see https://mega.nz/#F!c9AyURra!H4Oew0HB6JmqfPpmQ4SJqA
Click to expand...
Click to collapse
Hey, yes this should work. I think in the official kernel source from zte the config for wifi is missing.
Maybe they have done it any other way. Will cherry pick some commits and hope wifi will be alright then.

lightwars said:
Hey, yes this should work. I think in the official kernel source from zte the config for wifi is missing.
Maybe they have done it any other way. Will cherry pick some commits and hope wifi will be alright then.
Click to expand...
Click to collapse
If the blade is the same as the SU6, copy the pronto_wlan.ko module from stock to vendor/vodafone/p839v55/proprietary/lib/modules (or whatever you've named the directory structure) and in the BoardConfig.mk in the device tree put
BOARD_HAS_QCOM_WLAN := true
BOARD_WLAN_DEVICE := qcwcn
BOARD_HOSTAPD_DRIVER := NL80211
BOARD_HOSTAPD_PRIVATE_LIB := lib_driver_cmd_qcwcn
BOARD_WPA_SUPPLICANT_DRIVER := NL80211
BOARD_WPA_SUPPLICANT_PRIVATE_LIB := lib_driver_cmd_qcwcn
WIFI_DRIVER_MODULE_PATH := "/system/lib/modules/pronto/pronto_wlan.ko"
WIFI_DRIVER_MODULE_NAME := "wlan"
WPA_SUPPLICANT_VERSION := VER_0_8_X
That worked for the SU6.
(you might need something in the device.mk file I can't remember, give me a shout if this doesn't work).

in my cyanogenmode 12.1 for zte blade worked all. release version will be the end of the month

New Version with synced cm sources uploaded, wifi should know work.
Next step to get internal sdcard function properly and Sound working is very important.
Changes could effect that EU variant could work too, but I don't own one to test it. Please be careful.

So I think the button backlights will work in next version and I trying to get the sdcard working.
Why the sound is not working properly, I don't know at this time...

Check fortek's version may be, sound works fine there

So I got a newer build working, which has working audio. What is wired that sim card isn't detected, which seems as a problem.
Internal sdcard is accessible through file manager. And unfortunately button illumination do not work, which should be okay, I had done some tests before... So another build is needed which hopefully combine all things that work.

So.. Sim Card isnt working in this build?
And does it work properly on EU / DEU (german) Version?

DStyl3 said:
So.. Sim Card isnt working in this build?
And does it work properly on EU / DEU (german) Version?
Click to expand...
Click to collapse
Apparently yes, my sim card wasn't detected. A little bit strange, cause I didn't change so much, but anyway the other build is able of it.
I must admit that I don't own a EU or DEU version of this device, only the AS version. So I couldn't test the compatibility.
We need someone to test it to know for sure...
Update: New version is uploaded with sim working and sound... I apologize, cause I changed some vendor blobs and yes also some radio related ones, that's why it stopped working.

Great progress! Now just need the camera

eremini said:
Great progress! Now just need the camera
Click to expand...
Click to collapse
Back camera is working now, though I ran out of time getting all libs for the front camera. This will be next.
And to add it the builds only uses data/media and saddly not internal storage.

Storage issue is fixable?

eremini said:
Storage issue is fixable?
Click to expand...
Click to collapse
I think it is just a matter of mounting things right and playing with the init file.zte has just made some changes to their init files which differ from aosp.
In my opinion the better way is also to get one huge partition for userdata and data.Then what it is now,with two partitions...

lightwars said:
I think it is just a matter oft mounting rings right and playing with the init file.zte has just made some changes to their init files which differ from aosp.
In my opinion the better way is also to get one huge partition for userdata and data.Then what it is now,with two partitions...
Click to expand...
Click to collapse
Yeah I think that makes more sense. BTW serveral Russian users that tested ur firmware reported very weak wifi signal, up to the point where they couldn't connect to their wifi. May be something you want to look into.

eremini said:
Yeah I think that makes more sense. BTW serveral Russian users that tested ur firmware reported very weak wifi signal, up to the point where they couldn't connect to their wifi. May be something you want to look into.
Click to expand...
Click to collapse
Thanks for your information.That is not good. I used zte's driver...

This doesn't seem to work on the AU version... goes into a boot loop. Can anyone help?
Thanks a lot.

@lightwars , it is possible that the rom work for EU version ???, and if not, can you make it compatible ??

Android Nougat?

Does anyone know an eta or will it be even possible to make Nougat for the Galaxy S2 Plus?

there will be nougat versions.
Just wait

Nougat on S2p
No WiFi, BT, Audio, etc.

Carlos_Manuel said:
Nougat on S2p
No WiFi, BT, Audio, etc.
Click to expand...
Click to collapse
Where can I find the download link and can I flash this on GT-I9105P? Probably the thing that won't work is NFC but I don't use it anyways

Dinkec27 said:
Where can I find the download link and can I flash this on GT-I9105P? Probably the thing that won't work is NFC but I don't use it anyways
Click to expand...
Click to collapse
I haven't uploaded my nougat builds to anywhere yet. I've made several test builds and fixed some SELinux denials,etc. but there's still a lot to do.

Carlos_Manuel said:
I haven't uploaded my nougat builds to anywhere yet. I've made several test builds and fixed some SELinux denials,etc. but there's still a lot to do.
Click to expand...
Click to collapse
I will happily be your tester,if you want I can try to look for more issues,also great work on even making it bootable for the S2 Plus!

Dinkec27 said:
I will happily be your tester,if you want I can try to look for more issues,also great work on even making it bootable for the S2 Plus!
Click to expand...
Click to collapse
Here's a Nougat build for i9105:
https://drive.google.com/file/d/0B4Z8DsxsJxQqTmFrc0FSNm9ZamM/view?usp=sharing
I couldn't get BT,, Camera and WiFi working (just yet?).
in-earpiece speaker, microphone and sounds are working.
To fix RIL, flash the supersu,
http://techxat.com/download-supersu-android-7-0-nougat-root-package/
install root file manager (i.e. ES File Manager) (adb install, MTP, micro SD card or by some another method...)
Navigate to the system "/system/" and open build.prop.
Add these lines
Code:
rild.libpath=/system/lib/libbrcm_ril.so
ro.telephony.ril_class=SamsungBCMRIL
ro.telephony.call_ring.multiple=0
ro.telephony.call_ring=0
mobiledata.interfaces=rmnet0
to the build.prop below
"#
# ADDITIONAL_BUILD-PROPERTIES
#"
I am too lazy to make an another build with those props included
My next build will have those included in the build.prop.
Sources:
Device trees, vendor and kernel
https://github.com/manumanfred/android_device_samsung_galaxys2plus-common
https://github.com/manumanfred/android_device_samsung_i9105p
https://github.com/manumanfred/android_kernel_samsung_galaxys2plus-common
https://github.com/manumanfred/proprietary_vendor_samsung_galaxys2plus-common
ROM
https://github.com/Dreams-N

Carlos_Manuel said:
Here's a Nougat build for i9105:
https://drive.google.com/file/d/0B4Z8DsxsJxQqTmFrc0FSNm9ZamM/view?usp=sharing
I couldn't get BT,, Camera and WiFi working (just yet?).
in-earpiece speaker, microphone and sounds are working.
To fix RIL, flash the supersu,
http://techxat.com/download-supersu-android-7-0-nougat-root-package/
install root file manager (i.e. ES File Manager) (adb install, MTP, micro SD card or by some another method...)
Navigate to the system "/system/" and open build.prop.
Add these lines
Code:
rild.libpath=/system/lib/libbrcm_ril.so
ro.telephony.ril_class=SamsungBCMRIL
ro.telephony.call_ring.multiple=0
ro.telephony.call_ring=0
mobiledata.interfaces=rmnet0
to the build.prop below
"#
# ADDITIONAL_BUILD-PROPERTIES
#"
I am too lazy to make an another build with those props included
My next build will have those included in the build.prop.
Sources:
Device trees, vendor and kernel
https://github.com/manumanfred/android_device_samsung_galaxys2plus-common
https://github.com/manumanfred/android_device_samsung_i9105p
https://github.com/manumanfred/android_kernel_samsung_galaxys2plus-common
https://github.com/manumanfred/proprietary_vendor_samsung_galaxys2plus-common
ROM
https://github.com/Dreams-N
Click to expand...
Click to collapse
Thank you will test when I get home,great work!

Works very well except those features not working but who cares,I also noticed that the recent apps looks a bit weird,I wanted to take a screenshot but it doesn't work as well,anyways great work!

Dinkec27 said:
Works very well except those features not working but who cares,I also noticed that the recent apps looks a bit weird,I wanted to take a screenshot but it doesn't work as well,anyways great work!
Click to expand...
Click to collapse
Those looks weird, because I have not applied all the workarounds to fix rotation, screenshot, etc.

Can I somehow put Google Play on it because when I flash Gapps it bootloops?

Dinkec27 said:
Can I somehow put Google Play on it because when I flash Gapps it bootloops?
Click to expand...
Click to collapse
i tested the rom more opengapps pico and was booting fine

cracker12 said:
i tested the rom more opengapps pico and was booting fine
Click to expand...
Click to collapse
It was probably a bad download

Dinkec27 said:
Can I somehow put Google Play on it because when I flash Gapps it bootloops?
Click to expand...
Click to collapse
Sure, if you find correct gapps for it (use odexed ones), but most of the apps probably will fail to open. I'm working on the SElinux denials, but I'm not good at fixing denials... What I think, most of the SELinux rules should be made from scratch....
NFC and Bluetooth seems to be fworking now. :good:
But no sound, probably because of lib_Samsung_Resampler.so gets denied by audioserver, but in permissive SELinux mode audio should work (at least it worked and I am lazy to read my dumped logs)?
Now, also camera works (at least worked before witching to video recording and re-opening camera) and typo in hex-edited libwvn.so is fixed (symbol error).
Help from other more skilled/experienced users would be great.
Here's my new build:
https://drive.google.com/file/d/0B4Z8DsxsJxQqTHBJYlRYeEF2VVE/view?usp=sharing

Carlos_Manuel said:
Sure, if you find correct gapps for it (use odexed ones), but most of the apps probably will fail to open. I'm working on the SElinux denials, but I'm not good at fixing denials... What I think, most of the SELinux rules should be made from scratch....
NFC and Bluetooth seems to be fworking now. :good:
But no sound, probably because of lib_Samsung_Resampler.so gets denied by audioserver, but in permissive SELinux mode audio should work (at least it worked and I am lazy to read my dumped logs)?
Now, also camera works (at least worked before witching to video recording and re-opening camera) and typo in hex-edited libwvn.so is fixed (symbol error).
Help from other more skilled/experienced users would be great.
Here's my new build:
https://drive.google.com/file/d/0B4Z8DsxsJxQqTHBJYlRYeEF2VVE/view?usp=sharing
Click to expand...
Click to collapse
Great! I am not really skilled all that I've done is ported a lot of MTK ROMs and modified boot images,and ported recovery images,I tried maybe grabbing some libs from a Marshmallow ROM for S2 Plus and putting them in a flashable zip,but that ended up being a fail,the only thing that changed was it said that Wi-Fi is disabled,usually it would be blank lol

Btw did you add those lines for RIL to work to build.prop?

Yes, I did. I had screwed up one of my commits, that's why those lines didn't get included in my previous build.

[ROM] [UNOFFICIAL] LineageOS 13 for Life One X2-Mini [Discontinued]

LineageOS 13 for Life One X2 Mini​
This Rom was ported from the Unofficial LineageOS 13 for the Yureka Black. First I need to give credit for all the hard work the developers put into their Rom, I only modified it to work on the Blu Life One X2 Mini.
Note: Please remember I'm doing this on my own time and using my own money to cover expenses.
What Works:
(please let me know)
Camera
Fingerprint
SIM
Data
GPS
Audio
Video Playback
Sensors
Led
Not Working Yet:
(Please let me know)
FM Radio
Bluetooth
Latest Build: https://drive.google.com/open?id=0BzMHnGbQH3bheWVUNlFDNjljcEE
Builds: https://drive.google.com/drive/folders/0BzMHnGbQH3bhRXNUWi1jaGhDR3M?usp=sharing (list view recommended)
TWRP: https://drive.google.com/file/d/0BzMHnGbQH3bhTERvcGxlSkZFa2M/view?usp=sharing
Kernel:
Gapps: http://opengapps.org

Screenshots:

Changelog

Troubleshooting
Encryption Unsuccessful Screen:
Boot into TWRP and format Data (not wipe)

reserved 4

OK--it installs correctly, but after reboot it starts optimization & then screens up with encryption unsuccessful & wants to reset phone-goes to an open script to reformat/reset in TWRP--executes it & then reboots to the same again---this repeats as long as you allow it to. I tried installing twice-- the second time I wiped the phone completely---same result.

debianmain1 said:
OK--it installs correctly, but after reboot it starts optimization & then screens up with encryption unsuccessful & wants to reset phone-goes to an open script to reformat/reset in TWRP--executes it & then reboots to the same again---this repeats as long as you allow it to. I tried installing twice-- the second time I wiped the phone completely---same result.
Click to expand...
Click to collapse
Boot into TWRP and format Data (not wipe)

srgrusso said:
Boot into TWRP and format Data (not wipe)
Click to expand...
Click to collapse
Better choice , imho, would be to unpack the boot.img and change fstab to remove "forceencript"
edit:
sorry spoke too soon.
Just looked at fstab.qcom in boot.img and it is not set to "forceencrypt"

mrmazak said:
Better choice , imho, would be to unpack the boot.img and change fstab to remove "forceencript"
Click to expand...
Click to collapse
this is the current entry:
Code:
/dev/block/bootdevice/by-name/userdata /data ext4 nosuid,nodev,noatime,noauto_da_alloc wait,formattable,check,encryptable=footer;length=-16384
If I wanted to do that what would I change it too?
Thanks

OK--everything loaded & the phone booted normally. Wi-Fi is not working (deal-breaker for me--I use cellular data as little as possible--I have Wi-Fi everywhere I normally go.) Camera works-looks normal (using Google Camera)--works normally. Bluetooth is also not working.. (notice that Bluetooth Share has stopped). Screen & touch work normally. Right now I don't have cell service (that's the reason I use Wi-Fi quite a bit--all cell service is spotty where we live) & can't check cell data. If You could get the Wi-Fi to work, I could check quite a bit more......
More about the Wi-Fi: the MAC address looks like giberish---02:00:00:00:00:00

srgrusso said:
this is the current entry:
Code:
/dev/block/bootdevice/by-name/userdata /data ext4 nosuid,nodev,noatime,noauto_da_alloc wait,formattable,check,encryptable=footer;length=-16384
If I wanted to do that what would I change it too?
Thanks
Click to expand...
Click to collapse
I added an edit to my earlier post.
The way it is looks ok.
It can be encrypted, (encryptable=footer) but not being forced to be. (forceencrypt=)
The length and location of the encryption key would be important to get right, if force is used.

debianmain1 said:
OK--everything loaded & the phone booted normally. Wi-Fi is not working (deal-breaker for me--I use cellular data as little as possible--I have Wi-Fi everywhere I normally go.) Camera works-looks normal (using Google Camera)--works normally. Bluetooth is also not working.. (notice that Bluetooth Share has stopped). Screen & touch work normally. Right now I don't have cell service (that's the reason I use Wi-Fi quite a bit--all cell service is spotty where we live) & can't check cell data. If You could get the Wi-Fi to work, I could check quite a bit more......
More about the Wi-Fi: the MAC address looks like giberish---02:00:00:00:00:00
Click to expand...
Click to collapse
if your ready to do some more testing I should be able to get wifi working.

debianmain1 said:
OK--everything loaded & the phone booted normally. Wi-Fi is not working (deal-breaker for me--I use cellular data as little as possible--I have Wi-Fi everywhere I normally go.) Camera works-looks normal (using Google Camera)--works normally. Bluetooth is also not working.. (notice that Bluetooth Share has stopped). Screen & touch work normally. Right now I don't have cell service (that's the reason I use Wi-Fi quite a bit--all cell service is spotty where we live) & can't check cell data. If You could get the Wi-Fi to work, I could check quite a bit more......
More about the Wi-Fi: the MAC address looks like giberish---02:00:00:00:00:00
Click to expand...
Click to collapse
That type of address could be sign of either a corrupted NVRAM or incorrect radio firmware.
What do you have on the about screen for "baseband version"
and also on the about device/ status / IMEI information (do not list your numbers, just wheather or not they are there)

mrmazak said:
That type of address could be sign of either a corrupted NVRAM or incorrect radio firmware.
What do you have on the about screen for "baseband version"
and also on the about device/ status / IMEI information (do not list your numbers, just wheather or not they are there)
Click to expand...
Click to collapse
The rom is missing the kernel modules from the base rom. should be an easy fix. I already been through all this porting the same rom to th X2.
I might need to edit the boot image and build a script in bin to automaticly load the modules. I don't have a mini but as far as I can tell there is not much diffference from the X2.

srgrusso said:
The rom is missing the kernel modules from the base rom. should be an easy fix. I already been through all this porting the same rom to th X2.
I might need to edit the boot image and build a script in etc to automaticly load the modules. I don't have a mini but as far as I can tell there is not much diffference from the X2.
Click to expand...
Click to collapse
Sounds good---I need the phone for tomorrow, so I'm restoring it right now---will be ready to do more testing tomorrow night. As soon as I get working Wi-Fi I can get logcat up + the normal app load I use....then I could really test it---It looks real good so far.

mrmazak said:
That type of address could be sign of either a corrupted NVRAM or incorrect radio firmware.
What do you have on the about screen for "baseband version"
and also on the about device/ status / IMEI information (do not list your numbers, just wheather or not they are there)
Click to expand...
Click to collapse
This phone's kernel uses external modules, instead of built in like most kernels, odd choice by manufacture. system/lib/modules is missing, once the modules are added, and loaded wifi should work, just fine.

vampirefo said:
This phone's kernel uses external modules, instead of built in like most kernels, odd choice by manufacture. system/lib/modules is missing, once the modules are added, and loaded wifi should work, just fine.
Click to expand...
Click to collapse
So I would guess that will close the Wi-Fi & Bluetooth issues at the same time.

debianmain1 said:
Sounds good---I need the phone for tomorrow, so I'm restoring it right now---will be ready to do more testing tomorrow night. As soon as I get working Wi-Fi I can get logcat up + the normal app load I use....then I could really test it---It looks real good so far.
Click to expand...
Click to collapse
I have a new rom uploading now. It will be waiting for you when you are ready. Since you are using the stock rom could you please post the result of "lsmod" it will help me. Also after you boot the new rom could you please put the output of "dmesg" in a text file and post me a link or else just post it in pastbin. In order to get the adb shell working you'll need to change "the usb used for" from charging to file transfer.
Thanks

srgrusso said:
I have a new rom uploading now. It will be waiting for you when you are ready. Since you are using the stock rom could you please post the result of "lsmod" it will help me. Also after you boot the new rom could you please put the output of "dmesg" in a text file and post me a link or else just post it in pastbin. In order to get the adb shell working you'll need to change "the usb used for" from charging to file transfer.
Thanks
Click to expand...
Click to collapse
No problem---I also contacted the other guy that is interested in helping---should hear from him soon. Will download the new one & be ready for tomorrow.

Here is the new build. Hopefully it fixes Wifi.
https://drive.google.com/file/d/0BzMHnGbQH3bhenZNVE5MeEttVFk/view?usp=sharing

[ROM][UNOFFICIAL][7.1.2] Unlegacy Android Grouper Nougat [Nexus7 WIFI][12NOV2019]

I'm skipping 90% of words here because if you are here I assume you know what you are doing. And you can either Google, use the search button, or ask.
This is a private work of mine, that I use normally on my spare device. Supported as is.
Disclaimer:
Not responsible for any injuries you do to yourself or your device being damaged caused by this ROM.
Known issues:
- Camera not working
INSTRUCTIONS
Clean Flash
Download The ROM & GApps (pick latest one in drive, I use opengapps)
Wipe: System, Data, Dalvik, Cache
Flash ROM + GApps (Opengapps pico)
Reboot & Enjoy
Dirty Flash
Download the ROM
Wipe: Dalvik and Cache
Flash ROM (+Magisk if rooted previously or if want root)
Reboot & Enjoy
Download Folder Link:
https://drive.google.com/open?id=1D0Od55prO_Q_e8RY6QkZ-DjO36Qb188X (Pick Grouper)
Credits to:
Unlegacy Team

Initial Release:
May Security Patch

Can't download the ROM 404 error

JT1510365 said:
Can't download the ROM 404 error
Click to expand...
Click to collapse
https://drive.google.com/open?id=1usLQT6qkg8eUe3FwOvXXHRRaBF8VxR5H
This is the direct link for latest, thanks for trying out! cheers!

KiD3991 said:
https://drive.google.com/open?id=1usLQT6qkg8eUe3FwOvXXHRRaBF8VxR5H
This is the direct link for latest, thanks for trying out! cheers!
Click to expand...
Click to collapse
Which kernel you use?

TureX said:
Which kernel you use?
Click to expand...
Click to collapse
It's stock thus far, but I am testing out other things.

So I assume F2FS can't work, right?

New update:
Direct Link: https://drive.google.com/open?id=1ObhbiIgSwxIS3fDfb2AREEx_6syQSpi_
Consider this pre-June patch build. And no F2FS doesnt work @Stylez Ray. I am too noob to implement it. (For now)

Guys, I apologize but this month's upload will be slightly delayed due to my work and studies having major setbacks. Again, I apologize.

New update:
Direct Link: https://drive.google.com/open?id=1LkbL1TEupSYUY2zA_L_NklEP-j9xWDUP
Changes are minimal in this build other than using a better build machine lol

Thank's good job !!!
All works fine magisk v19.3, dax_axon7_v1.6.1.zip
I return on Andisa rom 7.1.2 freeze and lags horrible

This is really awesome, no more random system freezes like in the first official UA builds. Thanks a lot, it really makes this ancient device useful again ?

@KiD3991 hello, maybe you would like to join Unlegacy team as Tegra 3 developer?

Slightly odd request at this stage probably but is there any chance off an unlegacy lollipop build for grouper? with a 3.4 kernel please?
actually strike that the marshmellow build will be just fine
but does anyone know if shared memory is implemented in a chroot I get -
sysctl -w kernel.shmmax=268435456
returns cannot stat /proc/sys/kernel/shmmax: No such file or directory

New build up, sorry I was really unavailable.
I tried fixing a couple of things, see if it helps, do tell me though, mention me and I will show up.
Direct link: https://drive.google.com/open?id=1g4eu0ulizZ8ZO44hRjMUnIyEYIyWQL9t
Changelog:
Minor bug fixes
July Security Patch

curioct said:
Slightly odd request at this stage probably but is there any chance off an unlegacy lollipop build for grouper? with a 3.4 kernel please?
actually strike that the marshmellow build will be just fine
but does anyone know if shared memory is implemented in a chroot I get -
sysctl -w kernel.shmmax=268435456
returns cannot stat /proc/sys/kernel/shmmax: No such file or directory
Click to expand...
Click to collapse
Interesting for the marshmellow build. Does it have to be UL?
For the bottom one you gotta dig the right directory.

KiD3991 said:
Interesting for the marshmellow build. Does it have to be UL?
For the bottom one you gotta dig the right directory.
Click to expand...
Click to collapse
Hmm I've kind of slipped off this little project for a while I'm trying to use it with the newer kali builds chroot (requiring the 3.4 kernels I believe) in the hope of having a device with WiFi monitor mode available but I was running in to that shared memory issue with services such as postgresql etc think is was causing me issues with csploit too but as I say not really looked at it in a few weeks now.

curioct said:
Hmm I've kind of slipped off this little project for a while I'm trying to use it with the newer kali builds chroot (requiring the 3.4 kernels I believe) in the hope of having a device with WiFi monitor mode available but I was running in to that shared memory issue with services such as postgresql etc think is was causing me issues with csploit too but as I say not really looked at it in a few weeks now.
Click to expand...
Click to collapse
OMG SAME! I was trying with the Kali too on my other device. It was kinda confusing no doubt

This rom is working great, thanks. Please can anyone help me with how to install browser on this rom, as the USB is not working.

did u tried to activate the debug mode , in dev settings? if that doesn't work .. you have to switch the drivers by yourself, in windows ( devices manager ) from ADB Bootloader to Storage Device .. for your Nexus 7