Related
Hi all,
i noticed that GPS only works once after a reboot on this ROM.
Please note - This fix may work on any ROM, which uses tytung's GPS Libraries:
[26.Aug.2011][Dev] GPS Libraries v2.1 with AGPS support for HD2 Gingerbread
So even if your don't use dungphp RUNNYMEDE 1.05.401.4 - Android 2.3.5 - Sense 3.5 - it's worth a try to fix it this way.
You can fix it by modifying your gps.conf file from /system/etc/.
Note!
When modifying the file via ADB pull, its nessecary to set correct file permissions when pushed back to device by ADB.
Please note the original file permissions of gps.conf and ensure it has this permission settings when finshed editing the file.
There are alots of guides how to check/change file permissions on XDA/Google, so please read on this if your are not familiar to work on this.
e.g.:
Google: get set file permissions ADB
Google: get set file permissions ES Explorer
Pull your gps.conf file or edit it on device.
Your file should contain the parameter GPS1_CLEANUP_ENABLED=1 which it set to 1 by default.
If this parameter is missing in your file - add it.
Set the parameter to 0 (zero/off) .
It should look like this:
Code:
NTP_SERVER=yourCountryCode.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
SUPL_HOST=supl.google.com
SUPL_PORT=7276
###########################################
# Enable/disable automatic (periodic) #
# download requests of gpsOneXTRA #
# assistance data to client #
# Range: 0 to 1 #
# Default: 0 (Disabled) #
###########################################
GPS1_XTRA_AUTO_DOWNLOAD_ENABLED=1
###########################################
# Time (in hours) between automatic #
# download requests of gpsOneXTRA #
# assistance data to client #
# Range: 1 to 168 (168 = hr in a week) #
# Default: 24 hr #
###########################################
GPS1_XTRA_DOWNLOAD_INTERVAL=24
###########################################
# Enable/disable to shutdown the gpsOne #
# engine properly on GPS off #
# Range: 0 to 1 #
# Default: 1 (Enabled) #
###########################################
[COLOR="Red"]GPS1_CLEANUP_ENABLED=0[/COLOR]
###########################################
# Time (in seconds) between invoking #
# pdsm_get_position() #
# Range: 2 to 120 #
# Default: 2 seconds #
###########################################
GPS1_SESSION_TIMEOUT=2
Save your file or push it back to device and boot into CWM.
Don't forget to set the correct file permissions!
Thats it - reboot now.
GPS should work now everytime you need it.
Yours, Stephan
Is this just a bug with RUNNYMEDE? Because GPS works fine on HyperDroid with that enabled.
OCedHrt said:
Is this just a bug with RUNNYMEDE? Because GPS works fine on HyperDroid with that enabled.
Click to expand...
Click to collapse
Hi mate,
i tried it on 2 EU HD2 with this ROM - both showed the same behaviour - GPS didn't worked more than once before the fix and after fixing all was fine
I don't know if it's a problem on other ROMS, but it's worth a try when the ROM comes up with this particular symptom.
Greetz, Stephan
Nice man ! Thank you very much...
dungphp said:
Nice man ! Thank you very much...
Click to expand...
Click to collapse
Hi dungphp,
you are welcome
We have to thank you for your hard work on the ROMs!
Yours, Stephan
brush2 said:
Hi all,
i noticed that GPS only works once after a reboot on this ROM.
You can fix it by modifying your gps.conf file from /system/etc/.
Pull your gps.conf file or edit it on device.
Your file should contain the parameter GPS1_CLEANUP_ENABLED=1 which it set to 1 by default.
If this parameter is missing in your file - add it.
Set the parameter to 0 (zero/off) .
It should look like this:
Code:
NTP_SERVER=yourCountryCode.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
SUPL_HOST=supl.google.com
SUPL_PORT=7276
###########################################
# Enable/disable automatic (periodic) #
# download requests of gpsOneXTRA #
# assistance data to client #
# Range: 0 to 1 #
# Default: 0 (Disabled) #
###########################################
GPS1_XTRA_AUTO_DOWNLOAD_ENABLED=1
###########################################
# Time (in hours) between automatic #
# download requests of gpsOneXTRA #
# assistance data to client #
# Range: 1 to 168 (168 = hr in a week) #
# Default: 24 hr #
###########################################
GPS1_XTRA_DOWNLOAD_INTERVAL=24
###########################################
# Enable/disable to shutdown the gpsOne #
# engine properly on GPS off #
# Range: 0 to 1 #
# Default: 1 (Enabled) #
###########################################
[COLOR="Red"]GPS1_CLEANUP_ENABLED=0[/COLOR]
###########################################
# Time (in seconds) between invoking #
# pdsm_get_position() #
# Range: 2 to 120 #
# Default: 2 seconds #
###########################################
GPS1_SESSION_TIMEOUT=2
Save your file or push it back to device and boot into CWM.
Use the option menu Advanced then option Fix Permissions.
Thats it - reboot now.
GPS should work now everytime you need it.
Yours, Stephan
Click to expand...
Click to collapse
do we add ALL the text here you've written or just GPS1_CLEANUP_ENABLED=1,so sorry for the noob question lol
Ty5982 said:
do we add ALL the text here you've written or just GPS1_CLEANUP_ENABLED=1,so sorry for the noob question lol
Click to expand...
Click to collapse
LOL - hey mate,
of course only the parameter and it's value is required:
GPS1_CLEANUP_ENABLED=0
Btw: You wrote the parameter set to 1, this is the default value and is the reason for GPS failure.
This value must be set to 0 to get it to work!
I pasted the whole modified file here to show how it could/should look in the end.
Now we can see - even posting the whole file did not help in your case
Just kidding - have a nice day.
Greetz, Stephan
brush2 said:
LOL - hey mate,
of course only the parameter and it's value is required:
GPS1_CLEANUP_ENABLED=0
Btw: You wrote the parameter set to 1, this is the default value and is the reason for GPS failure.
This value must be set to 0 to get it to work!
I pasted the whole modified file here to show how it could/should look in the end.
Now we can see - even posting the whole file did not help in your case
Just kidding - have a nice day.
Greetz, Stephan
Click to expand...
Click to collapse
must apologise lol,early mornin here,not fully awake yet lol,was just curious as ive flashed loadsa fixes,even a gps fix apk floating around here and also faster fix that comes pre-installed,i've even edited my build prop,but nothing ever seems to work lol,but i've tried your solution,will use gps test from the market to see if anythings happening
EDIT: after this i get 9 sattelites in view 8 used,as before i didn't get any or if my phone was in a good mood i'd get 1 lol..........SO IT WORKS
Ty5982 said:
must apologise lol,early mornin here,not fully awake yet lol,was just curious as ive flashed loadsa fixes,even a gps fix apk floating around here,i've even edited my build prop,but nothing ever seems to work lol,but i've tried your solution,will use gps test from the market to see if anythings happening
Click to expand...
Click to collapse
Ok mate - good luck.
I hope i didn't promised too much
Would be nice to get some feedback from you - your info may help others!
Greetz, Stephan
brush2 said:
Ok mate - good luck.
I hope i didn't promised too much
Would be nice to get some feedback from you - your info may help others!
Greetz, Stephan
Click to expand...
Click to collapse
IT WORKS,IT WORKS,IT WORKS,IT WORKS,IT WORKS,IT WORKS,IT WORKS....................CAN'T SAY THANK YOU ENOUGH,i've got 4 bars signal as to the usual none and i aint even outside lol,will see when i take my little girl school in 15 min..........will tell u more then,feels like christmas has come early lol
Ty5982 said:
IT WORKS,IT WORKS,IT WORKS,IT WORKS,IT WORKS,IT WORKS,IT WORKS....................CAN'T SAY THANK YOU ENOUGH,i've got 4 bars signal as to the usual none and i aint even outside lol,will see when i take my little girl school in 15 min..........will tell u more then,feels like christmas has come early lol
Click to expand...
Click to collapse
Hugs from germany
Yours, Stephan
So using Dansta's Runnymede rom does that line get pasted at the end of the gps.conf info? Like the last line I mean.
chrisrj28 said:
So using Dansta's Runnymede rom does that line get pasted at the end of the gps.conf info? Like the last line I mean.
Click to expand...
Click to collapse
Hi mate,
maybe; - maybe means of course only if it does not exists upwards. I am not sure how it reacts if the parameter occurs twice with two different values - but i think the last occurence of this parameter in file should "win"
Greetz, Stephan
brush2 said:
Hugs from germany
Yours, Stephan
Click to expand...
Click to collapse
the english aren't suppose to like the germans lol,but u can be an exception lol.........my results using gps test from the market not GPS STATUS & TOOLBOX AS ITS NOT AS ACCURATE........
satellites in view 17
satellites used 15
accuracy(feet) 14.9
speed(mph) 0
NOT TO SURE HOW GOOD THESE RESULTS ARE,BUT THEY ARE 1000% BETTER THAN WHAT I USED TO GET
1 thing i did notice and is VERY IMPORTANT is if you have previously done a fix permissions for anything else,DELETE THE LOG SAVED ON YOUR SD CARD 1ST,add file to gps.config,save,reboot,then clickon fix permissions
Ty5982 said:
the english aren't suppose to like the germans lol,but u can be an exception lol.........my results using gps test from the market not GPS STATUS & TOOLBOX AS ITS NOT AS ACCURATE........
satellites in view 17
satellites used 15
accuracy(feet) 14.9
speed(mph) 0
NOT TO SURE HOW GOOD THESE RESULTS ARE,BUT THEY ARE 1000% BETTER THAN WHAT I USED TO GET
1 thing i did notice and is VERY IMPORTANT is if you have previously done a fix permissions for anything else,DELETE THE LOG SAVED ON YOUR SD CARD 1ST,add file to gps.config,save,reboot,then clickon fix permissions
Click to expand...
Click to collapse
Regarding "love between brits and germans" - i don't understand this is really a topic - damn; ain't there bigger problems in life?
The fix should not touch/change anything about accuracy. It only forces GPS to work as it should - .. more than once after a reboot...
Regarding deleting of fix permission log file - i don't think it has to be deleted to get the fix to work. But fixing the permissions is important to set the correct permissions for gps.conf file after modifying it.
Greetz, Stephan
brush2 said:
Regarding "love between brits and germans" - i don't understand this is really a topic - damn; ain't there bigger problems in life?
The fix should not touch/change anything about accuracy. It only forces GPS to work as it should - .. more than once after a reboot...
Regarding deleting of fix permission log file - i don't think it has to be deleted to get the fix to work. But fixing the permissions is important to set the correct permissions for gps.conf file after modifying it.
Greetz, Stephan
Click to expand...
Click to collapse
it works and that's all that matters
Why bother with CWR fix permissions as it can cause other issues (such as losing contact pictures in Messaging) - why not just edit the file with Root Explorer or ES Explorer, save and then longpress on the file and select properties and set all the permissions there? The file needs all nine boxes ticked for permissions. Also to make sure the file saves if you are using ES Explorer (not sure with Root Explorer) before you edit the file you need to go into settings and make sure you tick 'Mount system as writeable' otherwise it won't save.
Dunc001 said:
Why bother with CWR fix permissions as it can cause other issues (such as losing contact pictures in Messaging) - why not just edit the file with Root Explorer or ES Explorer, save and then longpress on the file and select properties and set all the permissions there? The file needs all nine boxes ticked for permissions. Also to make sure the file saves if you are using ES Explorer (not sure with Root Explorer) before you edit the file you need to go into settings and make sure you tick 'Mount system as writeable' otherwise it won't save.
Click to expand...
Click to collapse
Hi there,
You're right - it's more save only touching the permissions of gps.conf file. I will leave a note in the intial post to ensure people keep this in mind.
Thanks and Greetz, Stephan
OCedHrt said:
Is this just a bug with RUNNYMEDE? Because GPS works fine on HyperDroid with that enabled.
Click to expand...
Click to collapse
Look at the known issues #3 in my GPS thread for the reasons. It's there long time ago.
Some ROMs suffer from the "GPS off-and-on" bug.
Those ROMs can shutdown the gpsOne engine properly when turning off GPS setting using gps_cleanup(), but they cannot restart the gpsOne engine again because gps_init() is never called when turning GPS setting on after turning it off.
It's a Gingerbread bug which is fixed by applying this commit from the source code.
If you cannot modify the source code, the workaround is to set/add GPS1_CLEANUP_ENABLED=0 into gps.conf to avoid doing full cleanup.
Click to expand...
Click to collapse
tytung said:
Look at the known issues #3 in my GPS thread for the reasons. It's there long time ago.
Click to expand...
Click to collapse
I vaguely remember reading that But thanks always for your work.
20121219:
com.sec.enterprise.permissions
20121217:
2. Not much of a progress, argh. I have successfully activated Wallet 4 times on stock ROM without any restores. I can't seem to find any real pattern yet... :silly:
1. Finally SQL is installed, here is SQL binary for Jellybean.
Code:
[SIZE=2]adb shell mount -o rw,remount -t /dev/block/mmcblk0p13 /system
[/SIZE]adb push sqlite3 /system/xbin/sqlite3
adb chown root:root /system/xbin/sqlite3
adb shell chmod 744 /system/xbin/sqlite3
sqlite3 /data/data/com.android.providers.settings/databases/settings.db '.dump system'
20121212 Update:
My tests lol http://forum.xda-developers.com/showpost.php?p=35357763&postcount=275 See post# 263
20121211 Update2:
For now we can probably use ADB ... See post# 263
20121211 Update:
trying to install sqlite3...
I'll try figuring out what files we need to put in for built-in Google Wallet.
Will start with stock t-mobile rom.
Don't forget to hit Thanks if you learned something!
heart_crafter said:
I'll try figuring out what files we need to put in for built-in Google Wallet.
Will start with stock t-mobile rom.
From you guys I need you to login your google account and then go here
https://www.google.com/offers/m/manifest?mhlv=a.1&mhav=1.5-R87-v15&mhan=wallet
and let me know what links you get when you go there...
mine was as follows...
Make sure you mention what rom you are using.
Click to expand...
Click to collapse
On Jedi x6 here are the links I get
https://ad.doubleclick.net/activity
https://gan.doubleclick.net/gan_conversion
https://lh2.googleusercontent.com/public
https://lh3.googleusercontent.com/public
https://lh4.googleusercontent.com/public
https://lh5.googleusercontent.com/public
https://lh6.googleusercontent.com/public
https://lh2.ggpht.com
https://lh3.ggpht.com
https://lh4.ggpht.com
https://lh5.ggpht.com
https://lh6.ggpht.com
https://maps.googleapis.com/maps/api/staticmap
https://ssl.gstatic.com
https://ssl.google-analytics.com
https://apis.google.com/js
https://www.googleadservices.com/pagead/conversion
https://www.google.com/coupons
https://www.google.com/uds
heart_crafter said:
I'll try figuring out what files we need to put in for built-in Google Wallet.
Will start with stock t-mobile rom.
From you guys I need you to login your google account and then go here
https://www.google.com/offers/m/manifest?mhlv=a.1&mhav=1.5-R87-v15&mhan=wallet
and let me know what links you get when you go there...
mine was as follows...
Make sure you mention what rom you are using.
Click to expand...
Click to collapse
On Cmenard's 4.1.2 (N7105ZXXDLK7). Not sure if its any different than the Jedi x6 one posted above mine.
CACHE MANIFEST
# AppName: offers
# User: ***
# Version: 20a6f976c649f0ee
NETWORK:
*
/
https://ad.doubleclick.net/activity
https://gan.doubleclick.net/gan_conversion
https://lh2.googleusercontent.com/public
https://lh3.googleusercontent.com/public
https://lh4.googleusercontent.com/public
https://lh5.googleusercontent.com/public
https://lh6.googleusercontent.com/public
https://lh2.ggpht.com
https://lh3.ggpht.com
https://lh4.ggpht.com
https://lh5.ggpht.com
https://lh6.ggpht.com
https://maps.googleapis.com/maps/api/staticmap
https://ssl.gstatic.com
https://ssl.google-analytics.com
https://apis.google.com/js
https://www.googleadservices.com/pagead/conversion
https://www.google.com/coupons
https://www.google.com/uds
deodexed 4.1.1
CACHE MANIFEST
# AppName: offers
#
# Version: 20a6f976c649f0ee
NETWORK:
*
/
https://ad.doubleclick.net/activity
https://gan.doubleclick.net/gan_conversion
https://lh2.googleusercontent.com/public
https://lh3.googleusercontent.com/public
https://lh4.googleusercontent.com/public
https://lh5.googleusercontent.com/public
https://lh6.googleusercontent.com/public
https://lh2.ggpht.com
https://lh3.ggpht.com
https://lh4.ggpht.com
https://lh5.ggpht.com
https://lh6.ggpht.com
https://maps.googleapis.com/maps/api/staticmap
https://ssl.gstatic.com
https://ssl.google-analytics.com
https://apis.google.com/js
https://www.googleadservices.com/pagead/conversion
https://www.google.com/coupons
https://www.google.com/uds
rahilkalim is wallet working on your device?
No idea of they are the same but here is
XquiziT N2 Rom v8
AppName: offers # User: My Email # Version: 6d6105cc6a2c7f25
NETWORK: */ https://ad.doubleclick.net/activity
https://gan.doubleclick.net/gan_conversion
https://lh2.googleusercontent.com/public
https://lh3.googleusercontent.com/public
https://lh4.googleusercontent.com/public
https://lh5.googleusercontent.com/public
https://lh6.googleusercontent.com/public https://lh2.ggpht.com
https://lh3.ggpht.com
https://lh4.ggpht.com
https://lh5.ggpht.com
https://lh6.ggpht.com https://maps.googleapis.com/maps/api/staticmap
https://ssl.gstatic.com
https://ssl.google-analytics.com https://apis.google.com/js
https://www.googleadservices.com/pagead/conversion
https://www.google.com/coupons
https://www.google.com/uds
NETWORK: http://ssl.gstatic.com/m/og/ https://ssl.gstatic.com/m/og
Sent from my Galaxy Note 2
I am very sorry if I'm posting in the wrong thread, please, any mod, feel free to tell me and I'll remove and relocate right away.
I've searched Google, Bing, Yahoo, webcrawler, under my bed, and for the life of me, I can't seem to find how to get around this.
Here's what I did:
-Flashed 244 with flashtool.
-Rooted using DooMLoRD method
-Flashed CWM recovery
-Backed up with CWM recovery
-Copied the whole folder to my kitchen folder in Ubuntu.
-Joined the system.ext4.tar.a and system.ext4.tar.b into a single system.ext4.tar
-Started kitchen and chose that system.ext4.tar
-When chose told me it would use a fake boot.img, I said YES
-Created working folder
-An “update-script” was automatically created when extracting to working folder
-Rooted “superSU”
-BusyBox
Looks like this:
Working folder information (v0.224)
Android OS version : 4.2.2
Device : C6506
Model : C6506
ROM Name : 10.3.1.A.0.244
Rooted (Superuser app + su) : YES
Rooted (unsecured boot.img) : UNKNOWN
BusyBox installed : YES
BusyBox run-parts support : NO
Apps2SD (Apps to EXT) enabled : NO
/data/app enabled : NO
Custom boot animation allowed : NO
Nano text editor installed : NO
Bash shell support : NO
/system/framework is deodexed : NO
/system/app is deodexed : NO
radio.img found : NO
ROM will wipe all data : NO
Went to 0 “Advanced Options”
-Deodexed framework and App folders with API level 17 (4.2.2)
*********Had this error:
WARNING: Could not deodex the following (you can try to deodex these files again):
playstationcertified.odex
A summary of the deodexing has been logged in deodex_081413_155859.log
0 *.odex files remain in system/app
1 *.odex files remain in system/framework
******************************
-Zipaligned
-Added BusyBox Run-Parts feature
-Converted update-script to updater-script with options 0-17
-Build ROM from working folder, and it did find the updater-script(edify) while creating update.zip
Amazing, all good, tried to flash, it verifies the updater-scripts, opens the updater-script, then, TADAAAAAA, ERROR 0.
Don't know what it is I'm doing wrong.
Please, some wizard help me.
It worked like a charm when I was cooking for my HOX.
I'm guessing maybe I'm missing the edify_def file for ZL in the kitchen, or, there is something I'm missing for locked bootloaders, or, I'm just too dumb and too much of a noob to get it right, hahaha.
What?
work in progress build of AOSP, using LeJay's CM kernel sources and device files, modified to play ball with AOSP
some stuff copied from CM, to make build happen (bionic, assorted libs and stuff in external and system)
build makefiles modified, using CM files where possible
some small code modifications
for I9295 international only
stuff is broken, for how long i do not know. I'm still learning this stuff
DISCLAIMER: You take responsibility of your phone and what you flash into it, not me. You are warned
How?
grab the file: https://drive.google.com/folderview?id=0BzJzDM42pkRvcUVyZDRVSERzdlk&usp=sharing
if coming from another rom: factory reset + system format
upgrading previous version shouldn't need factory reset or system format
flash in CWM (yes, CWM or similar needed)
flash gapps
report bugs if new one found
help with development if possible
Credits
Google for Android (and Google search, boy this wouldn't have happened without it )
CyanogenMod for stuff i'm using to make this happen
SlimRom guys
LeJay for jactivelte kernel sources and other stuff
ohwarumbloss for testing CM builds and donations
Chainfire for root
other donators and testers
Changes v0.8
Video preview fixed
sub-1080p video recording fixed
Audio volume settings copied from SlimRom jf-common, more volume
Changes v0.7.1
Only kernel changes
Newer Broadcom wireless drivers from S4 CM 10.2 kernel
EXT4 and JBD2 drivers from S4 CM 10.2 kernel
MSM-8960 related stuff from S4 CM 10.2 kernel
Assorted stuff from S4 CM 10.2 kernel, check the commits in https://github.com/spegelius/android_kernel_samsung_jactivelte if interested (and if something seems wrong, please tell me
Changes v0.7
dualboot version available
network location working
backup to google account working. For those flashing cleanly, the setting should be on. For those dirtyflashing, you need to check this out: http://jftr.de/2014/01/fairphone-and-android-backups-to-the-google-cloud/
Changes v0.6
dualboot version available
some merges from S4 kernel, no changes in functionality
cwm update script doesn't format system anymore
libbt-vendor natively built instead copy from CM build. No change in functionality
Changes v0.5
Sdcard should now work (FAT32 at least, report exfat)
Sports Tracker doesn't crash UI when 'network' location provider isn't found
Changes v0.3 & 0.4
[*]Receiving calls fixed
Hanging up the call fixed
NFC doesn't crash on the background anymore, cannot test though
Bluetooth fixed, using lib from CM build
Changes v0.2
WiFi dhcp fixed
SuperSu included
init.d support
bash included
Bluetooth updates, but no full fix yet
Bugs v0.8
Whoa, are there any?
Bugs v0.7.1
Camera: 720p recording produces crappy videos
Camera: during video recording the preview is very low resolution
Bugs v0.6
Some problems with locations, network locaion isn't really enabled
Camera: 720p recording produces crappy videos
Camera: during video recording the preview is very low resolution
Backup account set to debug-only private cache for some users
Bugs v0.5
Some problems with locations
Camera: 720p recording produces crappy videos
Camera: during video recording the preview is very low resolution
Fixed Bugs
Sdcard doesn't mount
Cannot receive calls
Cannot hang up a call
WiFi connects, but doesn't get IP address
Bluetooth service fails at start, bluetooth doesn't work
NFC seems to be crashing on the background
no root as of yet
Source code
https://github.com/spegelius
Will be updating manifests and other stuff there when i figure a good way to get my changes there.
Oh and mods, if this fits the regular development section better, feel free to move it
A little incentive. Confirmation number: 1D974208B4414071D
I'll test and report. I'm on the GDE 4.2.2 port from Darkman now.
Downloading
Thank you very much for your efforts Mate!
Going to install this and report back soon!
Sent from my GT-I9295 using xda app-developers app
Edit1
Ok, here I come.
- Installation worked fine
- Bluetooth crashed on start as mentioned
- Mobile Data works (at least Edge, thats what I have here)
- WiFi get stuck in "Authenfication" when using standard settings
- WiFi connects when using "static IP" in advanced settings
- been to lazy to config Router for nonDHCP but I think it should work
- All SU Files (chainfire) I tried didn´t work (google search, no success, yet)
- No external SD, but that´s normal in AOSP I think (need 3rd Party app for this)
So, I started to compare this build with CM (cm-10.2-20131227-UNOFFICIAL-jactiveltexx) and there are several Files missing but there are so many..
@spegelius, if only I knew which ones are candidates for Problems...
Edit 2:
These Files may be interesting/important (Don´t laugh if this is totally wrong)
Missing Files in AOSP Build :
Code:
/system/app
- BluetoothExt.apk
Code:
/system/lib
- libbluedroid.so
- libcurve25519.so
- libimscamera_jni.so
- libjackpal-androidterm4.so
- liblzo.so
- libncurses.so
- libpci.so
- libssh.so
- libvt_jni.so
Code:
/system/lib/hw :
- nfc_nci.msm8960.so
- power.msm8960.so
Code:
/system/xbin
- bash
- htop
- Isof
- nano
- openvpn
- powertop
- rsync
- vim
There is no /system/etc/init.d (may be the/a problem of SU as there is also no "50selinuxrelabel" script)
There is no /system/etc/ssh (may be familar to the WiFi as it contains a script "sshd_config", inside this there is a lot of IP-Forwarding bla bla.. but all with a "#" in front)
I hope that helped a little or at all...I don´t have time for more investigations/testing for the rest of today, sorry..
Greetings
Thomas
ohwarumbloss said:
Downloading
Thank you very much for your efforts Mate!
Going to install this and report back soon!
Sent from my GT-I9295 using xda app-developers app
Edit1
Ok, here I come.
- Installation worked fine
- Bluetooth crashed on start as mentioned
- Mobile Data works (at least Edge, thats what I have here)
- WiFi get stuck in "Authenfication" when using standard settings
- WiFi connects when using "static IP" in advanced settings
- been to lazy to config Router for nonDHCP but I think it should work
- All SU Files (chainfire) I tried didn´t work (google search, no success, yet)
- No external SD, but that´s normal in AOSP I think (need 3rd Party app for this)
So, I started to compare this build with CM (cm-10.2-20131227-UNOFFICIAL-jactiveltexx) and there are several Files missing but there are so many..
@spegelius, if only I knew which ones are candidates for Problems...
Edit 2:
These Files may be interesting/important (Don´t laugh if this is totally wrong)
Missing Files in AOSP Build :
Code:
/system/app
- BluetoothExt.apk
Code:
/system/lib
- libbluedroid.so
- libcurve25519.so
- libimscamera_jni.so
- libjackpal-androidterm4.so
- liblzo.so
- libncurses.so
- libpci.so
- libssh.so
- libvt_jni.so
Code:
/system/lib/hw :
- nfc_nci.msm8960.so
- power.msm8960.so
Code:
/system/xbin
- bash
- htop
- Isof
- nano
- openvpn
- powertop
- rsync
- vim
There is no /system/etc/init.d (may be the/a problem of SU as there is also no "50selinuxrelabel" script)
There is no /system/etc/ssh (may be familar to the WiFi as it contains a script "sshd_config", inside this there is a lot of IP-Forwarding bla bla.. but all with a "#" in front)
I hope that helped a little or at all...I don´t have time for more investigations/testing for the rest of today, sorry..
Greetings
Thomas
Click to expand...
Click to collapse
Thanks for digging this stuff out. Some of those might be needed, i'l be adding them from CM repos one by one and testing how it works. I did another build, now adding Superuser to makefiles but still no go. Superuser does pop up after boot, telling su binary neds updating... Also added some init.rc scripts which are in CM build, but still no luck. After some digging, it seems that with 4.3, Google has made rooting bit more difficult. Root is my nr. 1 prio now, i'll need it to restore Titanium backups...
I've been using the rom few days now and it seems to work very well all in all. I had a camera hang yesterday, and after killing camera app it said Cannot connect to camera. Could get a logcat...
Yes, root is a problem, indeed..
Tried 3 hours yesterday in the evening, pushing all kind of different Versions and ended up with the binary update..
Also searched in CM Rom but it seems to be somewhere I can't find it, that little devil
ADB is working fine, also the shell with full root access, pushing and deleting Files, chown, all good. But no luck with the Superuser.apk.
Ended in frustration and restoring Stock..
Now, I hope you're getting it, somehow!
Did you get DHCP running somehow?
There are 3 PC and 4 Smartphones here using Wlan and I'm not really up to set them all up to static IP
Greetings
Thomas
Sent from my GT-I9295 using xda app-developers app
ohwarumbloss said:
Yes, root is a problem, indeed..
Tried 3 hours yesterday in the evening, pushing all kind of different Versions and ended up with the binary update..
Also searched in CM Rom but it seems to be somewhere I can't find it, that little devil
ADB is working fine, also the shell with full root access, pushing and deleting Files, chown, all good. But no luck with the Superuser.apk.
Ended in frustration and restoring Stock..
Now, I hope you're getting it, somehow!
Did you get DHCP running somehow?
There are 3 PC and 4 Smartphones here using Wlan and I'm not really up to set them all up to static IP
Greetings
Thomas
Sent from my GT-I9295 using xda app-developers app
Click to expand...
Click to collapse
Well i have the Superuser app as embedded in the rom and when starting TB, logcat shows that su binary tries to start, but fails with error:
D/su ( 2213): su invoked.
D/su ( 2214): starting daemon client 10062 10062
E/su ( 2215): connect failed with 2: No such file or directory
E/o.gZ ( 1909): Root shell has terminated unexpectedly.
Did a search of the error and it seems that it's related to root setting in developer options. The problem is, there's no setting for root in there. Gonna have to do some diffing between CM and AOSP settings.
Haven't looked into the dhcp yet.
To get root working:
install SuperSu: http://forum.xda-developers.com/showthread.php?t=1538053
Run in adb shell:
Code:
mount -o remount,rw /system
echo persist.sys.root_access=1 >> /system/build.prop
reboot
I'm trying to get supersu integrated, but latest from github doesn't like to play ball. Maybe i'll just use the above release and integrate it... Koush's Superuser doesn't display the dialog for root access when using CM's version and latest from github didn't find some symbols.
Edit: use value 3 if you want to give root access to apps and adb
Ok, some progress, even though i even lost root for a while. Damn i was losing my mind over it, but the it turned out to be a matter of su daemon not starting during boot. Added init.d support and proper init script for the daemon.
- wifi dhcp should work now. It was a matter of file permissions in /system/etc/dhcpd, run-hooks could not be executed. Noticed this when running dhcpd on adb shell. The cmw install script simply didn't set the perms...
- included SuperSu to rom, root should work out of the box
Bluetooth is still buggy; it doesn't fc on boot, but now it fails after a little while, this time the problem is that there's no /dev/ttyO1 for some reason and bt libs cannot connect to it.
Ver 0.2 is uploading, test away
spegelius said:
Ok, some progress, even though i even lost root for a while. Damn i was losing my mind over it, but the it turned out to be a matter of su daemon not starting during boot. Added init.d support and proper init script for the daemon.
- wifi dhcp should work now. It was a matter of file permissions in /system/etc/dhcpd, run-hooks could not be executed. Noticed this when running dhcpd on adb shell. The cmw install script simply didn't set the perms...
- included SuperSu to rom, root should work out of the box
Bluetooth is still buggy; it doesn't fc on boot, but now it fails after a little while, this time the problem is that there's no /dev/ttyO1 for some reason and bt libs cannot connect to it.
Ver 0.2 is uploading, test away
Click to expand...
Click to collapse
nice to here this , for bt issue are the ttyO1 file in ramdisk of boot.img?
mythi said:
nice to here this , for bt issue are the ttyO1 file in ramdisk of boot.img?
Click to expand...
Click to collapse
Hmm, haven't checked. I'll check that after work. I assume the vendor module is built properly as qcom's libs define ttyO1 and libbt_vendor.so exists. But shouldn't the ttyO1 ceated if the module is built?
spegelius said:
Hmm, haven't checked. I'll check that after work. I assume the vendor module is built properly as qcom's libs define ttyO1 and libbt_vendor.so exists. But shouldn't the ttyO1 ceated if the module is built?
Click to expand...
Click to collapse
Hmm... maybe tty01 is a qcom propriety so it couldnt be created without pulling it from a working device and place it in dev folder of ramdisk , I thought like this because the kernel extracts ramdisk files and folders in the "/" folder ..
mythi said:
Hmm... maybe tty01 is a qcom propriety so it couldnt be created without pulling it from a working device and place it in dev folder of ramdisk , I thought like this because the kernel extracts ramdisk files and folders in the "/" folder ..
Click to expand...
Click to collapse
Ok, could be. Don't know how ramdisk is created during build, have to look into it.
Also, found a quite major bug: cannot receive phone calls, at least i can't. That's kinda big problem, considering this is a phone still
Use dsixda kitchen to exreact the boot.img and view/edit its contents
mythi said:
Use dsixda kitchen to exreact the boot.img and view/edit its contents
Click to expand...
Click to collapse
Extracted boot.img, contents:
Code:
./zImage
./ramdisk
./ramdisk/init.trace.rc
./ramdisk/init.qcom.rc
./ramdisk/init.qcom.usb.sh
./ramdisk/system
./ramdisk/init.qcom.lpm_boot.sh
./ramdisk/sepolicy
./ramdisk/file_contexts
./ramdisk/seapp_contexts
./ramdisk/sbin
./ramdisk/sbin/ueventd
./ramdisk/sbin/adbd
./ramdisk/sbin/watchdogd
./ramdisk/init.cm.rc
./ramdisk/init.recovery.qcom.rc
./ramdisk/default.prop
./ramdisk/dev
./ramdisk/res
./ramdisk/res/images
./ramdisk/res/images/charger
./ramdisk/res/images/charger/battery_charge.png
./ramdisk/res/images/charger/battery_0.png
./ramdisk/res/images/charger/battery_fail.png
./ramdisk/res/images/charger/battery_5.png
./ramdisk/res/images/charger/battery_3.png
./ramdisk/res/images/charger/battery_4.png
./ramdisk/res/images/charger/battery_1.png
./ramdisk/res/images/charger/battery_2.png
./ramdisk/init.qcom.syspart_fixup.sh
./ramdisk/ueventd.qcom.rc
./ramdisk/charger
./ramdisk/sys
./ramdisk/init.qcom.class_main.sh
./ramdisk/init.usb.rc
./ramdisk/init.qcom.sh
./ramdisk/init.carrier.rc
./ramdisk/init.qcom.early_boot.sh
./ramdisk/ueventd.rc
./ramdisk/init.target.rc
./ramdisk/init.rc
./ramdisk/data
./ramdisk/init.qcom.class_core.sh
./ramdisk/init.qcom.usb.rc
./ramdisk/proc
./ramdisk/lpm.rc
./ramdisk/init
./ramdisk/property_contexts
./ramdisk/fstab.qcom
./ramdisk.cpio.gz
Nothing in /dev. Apparently those files are created by kernel/something else?
I'm feeling out of ideas currently, don't know where to start looking... i mean everything compiles ok, no errors. Logcat says:
Code:
I/bt_userial_vendor( 1515): userial vendor open: opening /dev/ttyO1
E/bt_userial_vendor( 1515): userial vendor open: unable to open /dev/ttyO1
E/bt_userial( 1515): userial_open: wrong numbers of open fd in vendor lib [0]!
E/bt_userial( 1515): userial_open: HCI UART expects only one open fd
From what i looked at bluedroid code, the tty opening should happen in vendor bt lib... meh. Same libs work with CM, i'm already using system/bluetooth and external/bluetooth from CM, along with qcom libs of course.
And about the phone, i can't seem to get apns to show, even though i copied proper apns list from CM. Even did a factory reset just to eliminate possibility about bad datas etc.
spegelius said:
Extracted boot.img, contents:
Code:
./zImage
./ramdisk
./ramdisk/init.trace.rc
./ramdisk/init.qcom.rc
./ramdisk/init.qcom.usb.sh
./ramdisk/system
./ramdisk/init.qcom.lpm_boot.sh
./ramdisk/sepolicy
./ramdisk/file_contexts
./ramdisk/seapp_contexts
./ramdisk/sbin
./ramdisk/sbin/ueventd
./ramdisk/sbin/adbd
./ramdisk/sbin/watchdogd
./ramdisk/init.cm.rc
./ramdisk/init.recovery.qcom.rc
./ramdisk/default.prop
./ramdisk/dev
./ramdisk/res
./ramdisk/res/images
./ramdisk/res/images/charger
./ramdisk/res/images/charger/battery_charge.png
./ramdisk/res/images/charger/battery_0.png
./ramdisk/res/images/charger/battery_fail.png
./ramdisk/res/images/charger/battery_5.png
./ramdisk/res/images/charger/battery_3.png
./ramdisk/res/images/charger/battery_4.png
./ramdisk/res/images/charger/battery_1.png
./ramdisk/res/images/charger/battery_2.png
./ramdisk/init.qcom.syspart_fixup.sh
./ramdisk/ueventd.qcom.rc
./ramdisk/charger
./ramdisk/sys
./ramdisk/init.qcom.class_main.sh
./ramdisk/init.usb.rc
./ramdisk/init.qcom.sh
./ramdisk/init.carrier.rc
./ramdisk/init.qcom.early_boot.sh
./ramdisk/ueventd.rc
./ramdisk/init.target.rc
./ramdisk/init.rc
./ramdisk/data
./ramdisk/init.qcom.class_core.sh
./ramdisk/init.qcom.usb.rc
./ramdisk/proc
./ramdisk/lpm.rc
./ramdisk/init
./ramdisk/property_contexts
./ramdisk/fstab.qcom
./ramdisk.cpio.gz
Nothing in /dev. Apparently those files are created by kernel/something else?
I'm feeling out of ideas currently, don't know where to start looking... i mean everything compiles ok, no errors. Logcat says:
Code:
I/bt_userial_vendor( 1515): userial vendor open: opening /dev/ttyO1
E/bt_userial_vendor( 1515): userial vendor open: unable to open /dev/ttyO1
E/bt_userial( 1515): userial_open: wrong numbers of open fd in vendor lib [0]!
E/bt_userial( 1515): userial_open: HCI UART expects only one open fd
From what i looked at bluedroid code, the tty opening should happen in vendor bt lib... meh. Same libs work with CM, i'm already using system/bluetooth and external/bluetooth from CM, along with qcom libs of course.
And about the phone, i can't seem to get apns to show, even though i copied proper apns list from CM. Even did a factory reset just to eliminate possibility about bad datas etc.
Click to expand...
Click to collapse
Hmmm.. Something is wrong lets reference to the stock kernel maybe we get answeres
:silly:
edit: Even stock kernel doesnt have have guess issue is different
---------- Post added at 09:50 PM ---------- Previous post was at 09:27 PM ----------
Looking at the logcat and staring at it for 20 minutes i think Logcats says
There is permission issue in the /system/vendor folder , missing bluetooth libs :cyclops: or simply permission issue
mythi said:
Hmmm.. Something is wrong lets reference to the stock kernel maybe we get answeres
:silly:
edit: Even stock kernel doesnt have have guess issue is different
---------- Post added at 09:50 PM ---------- Previous post was at 09:27 PM ----------
Looking at the logcat and staring at it for 20 minutes i think Logcats says
There is permission issue in the /system/vendor folder , missing bluetooth libs :cyclops: or simply permission issue
Click to expand...
Click to collapse
Heh, yes it might a permission issue, i've tried to match my updater-script perms to CM's, but not sure if they should be the same or something else. Suggestions welcome.
Edit: perms system:
Code:
drwxr-xr-x root root 2014-01-29 22:11 app
drwxr-xr-x root shell 2014-01-29 22:12 bin
-rw-r--r-- root root 3405 2008-08-01 15:00 build.prop
drwxr-xr-x root root 2014-01-29 22:11 cameradata
drwxr-xr-x root root 2014-01-29 22:11 etc
drwxr-xr-x root root 2014-01-29 22:11 fonts
drwxr-xr-x root root 2014-01-29 22:11 framework
drwxr-xr-x root root 2014-01-29 22:11 lib
drwxr-xr-x root root 1970-01-01 02:00 lost+found
drwxr-xr-x root root 2014-01-29 22:11 media
drwxr-xr-x root root 2014-01-29 22:11 tts
drwxr-xr-x root root 2014-01-29 22:11 usr
drwxr-xr-x root shell 2014-01-29 22:11 vendor
drwxr-xr-x root shell 2014-01-29 22:12 xbin
perms /system/vendor:
Code:
drwxr-xr-x root shell 2014-01-29 22:11 firmware
drwxr-xr-x root shell 2014-01-29 22:11 lib
perms /system/vendor/lib:
Code:
-rw-r--r-- root root 13880 2008-08-01 15:00 libbt-vendor.so
perms /system/vendor/firmware:
Code:
-rw-r--r-- root root 9432 2008-08-01 15:00 bcm2079xB4_firmware.ncd
-rw-r--r-- root root 783 2008-08-01 15:00 bcm2079xB4_pre_firmware.ncd
-rw-r--r-- root root 47921 2008-08-01 15:00 bcm4335.hcd
-rw-r--r-- root root 28862 2008-08-01 15:00 bcm4335_A0.hcd
-rw-r--r-- root root 47921 2008-08-01 15:00 bcm4335_murata.hcd
-rw-r--r-- root root 70 2008-08-01 15:00 bcm4335_prepatch.hcd
-rw-r--r-- root root 47921 2008-08-01 15:00 bcm4335_semco.hcd
Maybe i'll need to set them root:shell in vendor?
spegelius said:
Heh, yes it might a permission issue, i've tried to match my updater-script perms to CM's, but not sure if they should be the same or something else. Suggestions welcome.
Edit: perms system:
Code:
drwxr-xr-x root root 2014-01-29 22:11 app
drwxr-xr-x root shell 2014-01-29 22:12 bin
-rw-r--r-- root root 3405 2008-08-01 15:00 build.prop
drwxr-xr-x root root 2014-01-29 22:11 cameradata
drwxr-xr-x root root 2014-01-29 22:11 etc
drwxr-xr-x root root 2014-01-29 22:11 fonts
drwxr-xr-x root root 2014-01-29 22:11 framework
drwxr-xr-x root root 2014-01-29 22:11 lib
drwxr-xr-x root root 1970-01-01 02:00 lost+found
drwxr-xr-x root root 2014-01-29 22:11 media
drwxr-xr-x root root 2014-01-29 22:11 tts
drwxr-xr-x root root 2014-01-29 22:11 usr
drwxr-xr-x root shell 2014-01-29 22:11 vendor
drwxr-xr-x root shell 2014-01-29 22:12 xbin
perms /system/vendor:
Code:
drwxr-xr-x root shell 2014-01-29 22:11 firmware
drwxr-xr-x root shell 2014-01-29 22:11 lib
perms /system/vendor/lib:
Code:
-rw-r--r-- root root 13880 2008-08-01 15:00 libbt-vendor.so
perms /system/vendor/firmware:
Code:
-rw-r--r-- root root 9432 2008-08-01 15:00 bcm2079xB4_firmware.ncd
-rw-r--r-- root root 783 2008-08-01 15:00 bcm2079xB4_pre_firmware.ncd
-rw-r--r-- root root 47921 2008-08-01 15:00 bcm4335.hcd
-rw-r--r-- root root 28862 2008-08-01 15:00 bcm4335_A0.hcd
-rw-r--r-- root root 47921 2008-08-01 15:00 bcm4335_murata.hcd
-rw-r--r-- root root 70 2008-08-01 15:00 bcm4335_prepatch.hcd
-rw-r--r-- root root 47921 2008-08-01 15:00 bcm4335_semco.hcd
Maybe i'll need to set them root:shell in vendor?
Click to expand...
Click to collapse
try making perms in vendor as root excute user and group (i think in other words it is root:shell) this will inusre if we have perm issue
mythi said:
try making perms in vendor as root excute user and group (i think in other words it is root:shell) this will inusre if we have perm issue
Click to expand...
Click to collapse
No go with relaxed permissions, even set the x bit on... also noticed that /system/etc/bluetooth had some strange permissions, but no change.
I noticed that there are some bluetooth related devices in /dev, like ttyHS0 so it isn't fully dead. The problem is to find out why the damn ttyO1 won't start... actuallu i'm not liking the current state where i use most of the Bluetooth implemntation from CM. What i'd like is to have as close to AOSP as possible. Maybe i'll need to start cherrypicking parts of the bluetooth code and take only needed stuff to support qcom chips. But that'll take a while to get working.
Oh and stumbled upon some telephony code in framework/opt/telephony. Saw some files like SamungQualcom in CM sources, which indicates that to get phone working, checking through that code is needed. Quick compare showed some 100 files are different, so there;s work there too...
spegelius said:
No go with relaxed permissions, even set the x bit on... also noticed that /system/etc/bluetooth had some strange permissions, but no change.
I noticed that there are some bluetooth related devices in /dev, like ttyHS0 so it isn't fully dead. The problem is to find out why the damn ttyO1 won't start... actuallu i'm not liking the current state where i use most of the Bluetooth implemntation from CM. What i'd like is to have as close to AOSP as possible. Maybe i'll need to start cherrypicking parts of the bluetooth code and take only needed stuff to support qcom chips. But that'll take a while to get working.
Oh and stumbled upon some telephony code in framework/opt/telephony. Saw some files like SamungQualcom in CM sources, which indicates that to get phone working, checking through that code is needed. Quick compare showed some 100 files are different, so there;s work there too...
Click to expand...
Click to collapse
Why dont we cherry pick from gs4 snapdragon version qcom things since they share the same board , just cherry pick the diver files from an aosp rom for that device I am quite sure it will work .
Sent from my GT-I9295 using Tapatalk
Don't give up!
Let me know if there's something I can do!
Saturday 95℅ free time if the weather doesn't turn to warm (bike is calling)
Sent from my GT-I9295 using xda app-developers app
ElementalX Kernel
for Moto G4 and G4 Plus
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ElementalX is designed for maximum stability. It is made for people who depend on their phone every day.
Features
Easy installation and setup with Aroma installer
Fingerprint sensor as home button
Sweep2sleep
Block wakelocks
Rootable
Sound control
Overclock or underclock CPU
NTFS r/w support
Option to disable fsync
advanced color control
performance and power optimizations
upstream ZRAM with lz4 compression
KSM enabled
brighter HBM
adjust or disable vibration
FIOPS i/o scheduler
Does not modify system partition
Does not overwrite modules
Compatible with systemless root
Installation
1. Flash in recovery
For maximum compatibility with all ROMs, ElementalX uses your existing ramdisk.
Notes
This works on both the G4 and the G4 Plus but NOT the G4 Play.
Flashing this does not modify your system partition, only the boot.img. Back up your stock boot.img in recovery or with an app and you can easily restore it if you want to return to stock or install OTAs.
EX Kernel Manager can be used to configure settings and install or update the kernel.
You can also use my free app Button Mapper to customize the actions of the fingerprint sensor if you have the G4 Plus
Google+ Community
Download
Stock Android 8.1.0 Oreo
ElementalX-G4-3.01
Stock Android 7.0
ElementalX-G4-2.01
LineageOS-based Android 7..1.1/7.1.2
ElementalX-G4-1.11-LOS
Stock Android 6.0.1
ElementalX-G4-0.07
CM-based Android 6.0.1
ElementalX-G4-0.07-cm
Source code
https://github.com/flar2/kernel-msm
_____________________________________
XDA:DevDB Information
ElementalX-G4, Kernel for the Moto G4 Plus
Contributors
flar2
Source Code: https://github.com/flar2/kernel-msm
Kernel Special Features:
Version Information
Status: Stable
Created 2016-07-24
Last Updated 2019-03-21
Reserved
0.02:
-build optimizations (linaro 4.9 -O2)
-headphone gain control
0.01:
-Fingerprint sensor as home button
-Sweep2sleep
-Overclock or underclock CPU
-NTFS r/w support
-Option to disable fsync
-advanced color control
-performance and power optimizations
-upstream ZRAM with lz4 compression
-KSM enabled
-brighter HBM
-adjust or disable vibration
-FIOPS i/o scheduler
Reserved
Hi, I have not worked WiFi.
wizard-dima said:
Hi, I have not worked WiFi.
Click to expand...
Click to collapse
Please tell me your model number and build number from the about phone page in settings.
flar2 said:
Please tell me your model number and build number from the about phone page in settings.
Click to expand...
Click to collapse
G4 plus XT1642
build number - MPJ24.139-48
You can add doubletap2wake?
Sweep2sleep only works right to left.
Although I chose to either side.
wizard-dima said:
G4 plus XT1642
build number - MPJ24.139-48
You can add doubletap2wake?
Sweep2sleep only works right to left.
Although I chose to either side.
Click to expand...
Click to collapse
I would also like to see the output of
Code:
lsmod
from adb shell or terminal.
WiFi working and no issues so far
Moto G4
XT1625
BUILD- MPJ24.139-49
LSMOD OUTPUT
Module Size Used by
wlan 4215738 0
core_ctl 20182 0
qdrbg_module 30626 0
qcrypto_module 145880 0
flar2 said:
I would also like to see the output of
Code:
lsmod
from adb shell or terminal.
Click to expand...
Click to collapse
You kernel:
Module Size Used by
qdrbg_module 30626 0
qcrypto_module 145880 0
Stock kernel:
Module Size Used by
core_ctl 20182 0
wlan 4215738 0
qdrbg_module 30626 0
qcrypto_module 145880 2
zanoli99 said:
WiFi working and no issues so far
Moto G4
XT1625
BUILD- MPJ24.139-49
LSMOD OUTPUT
Module Size Used by
wlan 4215738 0
core_ctl 20182 0
qdrbg_module 30626 0
qcrypto_module 145880 0
Click to expand...
Click to collapse
perfect, thanks!
wizard-dima said:
Module Size Used by
qdrbg_module 30626 0
qcrypto_module 145880 0
Click to expand...
Click to collapse
One more question:
Can you show me the output of these commands:
Code:
ls -la /system/lib/modules/
Code:
su -c insmod /system/lib/modules/wlan.ko
flar2 said:
One more question:
Can you show me the output of these commands:
Code:
ls -la /system/lib/modules/
D:\ADB>adb shell ls -la /system/lib/modules/
-rw-r--r-- root root 9404 2009-01-01 09:00 ansi_cprng.ko
-rw-r--r-- root root 128788 2009-01-01 09:00 core_ctl.ko
-rw-r--r-- root root 8736 2009-01-01 09:00 dma_test.ko
-rw-r--r-- root root 6400 2009-01-01 09:00 evbug.ko
-rw-r--r-- root root 6592 2009-01-01 09:00 gpio_axis.ko
-rw-r--r-- root root 7216 2009-01-01 09:00 gpio_event.ko
-rw-r--r-- root root 9712 2009-01-01 09:00 gpio_input.ko
-rw-r--r-- root root 10648 2009-01-01 09:00 gpio_matrix.ko
-rw-r--r-- root root 4200 2009-01-01 09:00 gpio_output.ko
-rw-r--r-- root root 228528 2009-01-01 09:00 isdbt.ko
-rw-r--r-- root root 43304 2009-01-01 09:00 mcDrvModule.ko
-rw-r--r-- root root 20608 2009-01-01 09:00 mcKernelApi.ko
-rw-r--r-- root root 47104 2009-01-01 09:00 mmc_block_test.ko
-rw-r--r-- root root 36916 2009-01-01 09:00 mmc_test.ko
-rw-r--r-- root root 44852 2009-01-01 09:00 oprofile.ko
drwxr-xr-x root root 2009-01-01 09:00 pronto
-rw-r--r-- root root 18088 2009-01-01 09:00 spidev.ko
-rw-r--r-- root root 28816 2009-01-01 09:00 test-iosched.ko
lrw-r--r-- root root 2009-01-01 09:00 wlan.ko -> /system/lib/mo
dules/pronto/pronto_wlan.ko
Code:
su -c insmod /system/lib/modules/wlan.ko
Click to expand...
Click to collapse
D:\ADB>adb shell su -c insmod /system/lib/modules/wlan.ko
insmod: failed to load /system/lib/modules/wlan.ko: File exists
wizard-dima said:
D:\ADB>adb shell su -c insmod /system/lib/modules/wlan.ko
insmod: failed to load /system/lib/modules/wlan.ko: File exists
Click to expand...
Click to collapse
I should have mentioned this, I need that output withe ElementalX installed.
flar2 said:
I should have mentioned this, I need that output withe ElementalX installed.
Click to expand...
Click to collapse
Sorry, WiFi works.
The problem was that during the first installation I did not have root access.
For the team of your su needed the right, so that's posleh their installation, with no WiFi key problems.
I think it is necessary to specify in the instructions, and a large red font)
wizard-dima said:
Sorry, WiFi works.
The problem was that during the first installation I did not have root access.
For the team of your su needed the right, so that's posleh their installation, with no WiFi key problems.
I think it is necessary to specify in the instructions, and a large red font)
Click to expand...
Click to collapse
Thanks for the head's up.
So without root, no wifi.
I'll see if I can fix that.
on the standard firmware, the phone spends too much charge in sleep mode. You can it somehow fix it?
I don't think I can get the wifi module to load without root.
The problem is I need to mount an image at /system/lib/modules but selinux won't allow it. It is only possible with SuperSu installed unless somebody knows how to modify sepolicy without SuperSU.
wizard-dima said:
on the standard firmware, the phone spends too much charge in sleep mode. You can it somehow fix it?
Click to expand...
Click to collapse
I'm not sure what you mean?
flar2 said:
I'm not sure what you mean?
Click to expand...
Click to collapse
You can add doubletap2wake?
wizard-dima said:
You can add doubletap2wake?
Click to expand...
Click to collapse
I don't know. I think it might cause battery drain on this device. There also isn't a big need for it since the fingerprint sensor is on the front and wakes up the device (at least on the G4 Plus)
working perfectly..thanks bro.
WiFi working ..now i can able to use finger print sensor as home button..thank very much bro..
Moto G4 plus
XT1643
BUILD- MPJ24.139-23.1
LSMOD OUTPUT
Module Size Used by
wlan 4215738 0
core_ctl 20182 0
qdrbg_module 30626 0
qcrypto_module 145880 0