So I have a fairly large host of problems on my LG G5 H830. I've tried a total of 3 different roms, and most of the problems have persisted throughout each rom.
Resurrection Remix:
NFC will not turn on, switch moves but it stays greyed out and does not activate NFC.
Magisk Manager periodically unroots; I have to reflash the MagiskManager zip in TWRP about twice a day.
Storage manager shows that I have 16gb total internal storage (I have 32), so it shows that I am using a negative amount of space on my drive.
System Process sometimes stops responding, causing the lock screen to not show and allowing anyone to access my phone for a short time.
Whenever I try train my voice model for Google Assistant, the Google app stops responding before crashing. This means that I can't get the "OK Google" prompt to work.
My battery sometimes simply fails to charge. For example, I charged my phone overnight, and the battery graph shows that it charged to about 50% or so before dropping back to about 20% and staying there until I noticed in the morning.
AICP:
Storage manager shows that I have 16gb total internal storage (I have 32), so it shows that I am using a negative amount of space on my drive.
(I haven't tested Google Assistant, and haven't had the System Process or battery drain issues - but I didn't have the rom installed long enough to truly test.)
Xenon HD:
NFC will not turn on, switch moves but it stays greyed out and does not activate NFC.
Storage manager shows that I have 16gb total internal storage (I have 32), so it shows that I am using a negative amount of space on my drive.
(As with AICP, I didn't install the rom for very long and did not test for the Google Assistant, System Process, or battery drain issues.)
The one problem that persisted through each rom was the incorrect display of storage capacity and usage, but TWRP has no problems with this. It also has no problem with charging. In addition, I've tried resizing, repairing, and re-formatting to EXT4 on my system, Data, and cache partitions. I don't know what else to try at this point, but since TWRP doesn't work any differently than I'd expect, it doesn't seem to me like a hardware issue - but then, I'm not an expert by any means, which is why I'm opening this thread.
Gannondalf said:
So I have a fairly large host of problems on my LG G5 H830. I've tried a total of 3 different roms, and most of the problems have persisted throughout each rom.
Resurrection Remix:
NFC will not turn on, switch moves but it stays greyed out and does not activate NFC.
Magisk Manager periodically unroots; I have to reflash the MagiskManager zip in TWRP about twice a day.
Storage manager shows that I have 16gb total internal storage (I have 32), so it shows that I am using a negative amount of space on my drive.
System Process sometimes stops responding, causing the lock screen to not show and allowing anyone to access my phone for a short time.
Whenever I try train my voice model for Google Assistant, the Google app stops responding before crashing. This means that I can't get the "OK Google" prompt to work.
My battery sometimes simply fails to charge. For example, I charged my phone overnight, and the battery graph shows that it charged to about 50% or so before dropping back to about 20% and staying there until I noticed in the morning.
AICP:
Storage manager shows that I have 16gb total internal storage (I have 32), so it shows that I am using a negative amount of space on my drive.
(I haven't tested Google Assistant, and haven't had the System Process or battery drain issues - but I didn't have the rom installed long enough to truly test.)
Xenon HD:
NFC will not turn on, switch moves but it stays greyed out and does not activate NFC.
Storage manager shows that I have 16gb total internal storage (I have 32), so it shows that I am using a negative amount of space on my drive.
(As with AICP, I didn't install the rom for very long and did not test for the Google Assistant, System Process, or battery drain issues.)
The one problem that persisted through each rom was the incorrect display of storage capacity and usage, but TWRP has no problems with this. It also has no problem with charging. In addition, I've tried resizing, repairing, and re-formatting to EXT4 on my system, Data, and cache partitions. I don't know what else to try at this point, but since TWRP doesn't work any differently than I'd expect, it doesn't seem to me like a hardware issue - but then, I'm not an expert by any means, which is why I'm opening this thread.
Click to expand...
Click to collapse
Pretty much every issue you're having has been documented already, so it's not your phone.
1) NFC is completely broken on h830 in custom ROMs.
2) Magisk works fine, stop using magisk hide and built in magisk busy box, it will hide root from itself. This is a magisk issue not a ROM issue. If you need busy box download it from play store.
3) Storage size being incorrectly shown had been the case ever since cm 14.1 became available and therefore affects all Los based ROMs.
4) Don't use Google Assistant but others have stated there are issues with it.
5) Make sure after rebooting to unplug and replug your charger or it won't charge.
6) If it was a clean flash and you installed correct gapps, you shouldn't have system processes force closing. Make sure your using opengapps 7.1, arm64 and newest version available and nano or pick version.
The above issues affect basically every lineage os based ROM currently. Hopefully this helps
jeffsga88 said:
Pretty much every issue you're having has been documented already, so it's not your phone.
1) NFC is completely broken on h830 in custom ROMs.
2) Magisk works fine, stop using magisk hide and built in magisk busy box, it will hide root from itself. This is a magisk issue not a ROM issue. If you need busy box download it from play store.
3) Storage size being incorrectly shown had been the case ever since cm 14.1 became available and therefore affects all Los based ROMs.
4) Don't use Google Assistant but others have stated there are issues with it.
5) Make sure after rebooting to unplug and replug your charger or it won't charge.
6) If it was a clean flash and you installed correct gapps, you shouldn't have system processes force closing. Make sure your using opengapps 7.1, arm64 and newest version available and nano or pick version.
The above issues affect basically every lineage os based ROM currently. Hopefully this helps
Click to expand...
Click to collapse
Thanks a lot for clearing this up! I'll take those suggestions and see if I have any luck (especially with the battery charging issue, since I mostly figured the other ones out on my own). I just came from a Moto G3 with RR, which seems to be a lot more stable than the H830, so all this at once caught me by surprise a bit.
Again, I appreciate your help with this.
Gannondalf said:
Thanks a lot for clearing this up! I'll take those suggestions and see if I have any luck (especially with the battery charging issue, since I mostly figured the other ones out on my own). I just came from a Moto G3 with RR, which seems to be a lot more stable than the H830, so all this at once caught me by surprise a bit.
Again, I appreciate your help with this.
Click to expand...
Click to collapse
No problem. By the way, I think RR is probably the best custom ROM for our device overall, especially if you like customizations But, they're are still some issues. Another issue to be aware of is that on Los based ROMs the camera isn't anyways saving videos (messed up part is that this only started happening in last month or so, it worked fine before that lol).
Gannondalf said:
Thanks a lot for clearing this up! I'll take those suggestions and see if I have any luck (especially with the battery charging issue, since I mostly figured the other ones out on my own). I just came from a Moto G3 with RR, which seems to be a lot more stable than the H830, so all this at once caught me by surprise a bit. Again, I appreciate your help with this.
Click to expand...
Click to collapse
Just an honest opinion. You shouldn't have got a LG G5 if your intention was to use AOSP roms. You could get a Moto Z Play, or a Moto G5 Plus.
LG and Samsung phones would always have issues on AOSP roms.
suhridkhan said:
Just an honest opinion. You shouldn't have got a LG G5 if your intention was to use AOSP roms. You could get a Moto Z Play, or a Moto G5 Plus.
LG and Samsung phones would always have issues on AOSP roms.
Click to expand...
Click to collapse
I'm starting to realize that. I got it based off of the design (which I really like, especially with the rear fingerprint scanner) and the specs, and didn't do much more research than seeing that there were confirmed methods of installing custom roms. But, at this point, I can't return it and I'm more interested in getting it to work as best as I can.
Related
Common ICS Problems
If you plug in USB while your tablet is asleep you will have a SOD
Installation Problems
Install tips from tlb1961 here and lyricalpapa in post #3
Try not to use any backup's as they cause many problems.
Make sure your using CWM 5.5.0.4 Beta 15 (comes with the nvflash in TeamDRH ICS thread)
On your first boot let it sit for 30-60min (the longer, the better) and then reset.
If all else fails try this
Th3DmaN's G-Tablet Tools for anyone who is having trouble connecting and flashing their G-Table
Speed Problems
Different launchers such as Apex or Nova or any compatible launcher may or may not increase smoothness. There is no problem with installing them on top of the stock launcher as only one launcher runs at a time.
Battery and Power Problems
Your tablet went to sleep and wont wake up, try pushing the power button a couple of times and wait 5 seconds inbetween presses.
Your tablet has completely frozen, try pushing the power button for 30+ seconds. If that doesn't do it, you can leave your tablet alone for a couple hours and try again (may or may not work) or you can wait till the battery dies or if your impatient you can open the tablet up and press the internal reset, it looks like this. Here are some helpful pictures and a video for opening it up. If you have no reset button you will need to disconnect the battery, here's what it looks like. If you do get a SOD do this to help the developers.
Connection & Browser Problems
WiFi not working, try to "forget" the WiFi and re-enter your password. Also can try resetting your router or changing the security. Some say ICS does not like high channels.
If your having market errors, try force closing and clearing the cache in settings\apps\all. If that doesn't work then find every market reference and force close then clear the cache and reset.
Your computer doesn't recognize your tablet, you will need MTP drivers read the ICS rom page again. For Windows XP you need to disable debugging. For linux try Th3DmaN's guide.
Adhoc does not work with this build.
Stock browser seems to lock up after a bit. Possible fix is to disable java. Thanks plastikman
Screen and Sound Problems
1080p on H/W? Use Handbrake and import this profile. Here's the high profile settings for 720p, for those wanting the best quality.
Videoplayers such as MxVideo player, can play H/W video but the sound will need to be changed to S/W.
Icons and text too small? Try using this guide. CAUTION Changing the DPI really messes with the Market.
DSP Manager has been causing slowness/audio problems. Try stopping it to see if that's the problem. You can delete it safely if causing problems.
Game and Apps Problems
Alot of games and apps are not updated for ICS yet so they won't work correctly.
Hulu flash hack here. It should work. Anyone with Hulu can you post your results.MAY NOT WORK ANYMORE
Bypassing Exchange Security Policy try this
Connecting the ICS Mail app to Microsoft's Cloud hosted Exchange services check here
Gamepad support - follow jazzruby's guide here
Miscellaneous Problems
Errors popping up constantly, you need to reinstall again and make sure this time you erase everything.
Nandroid backups, you need to follow this guide
Important Notes
The SOD (sleep of death) we talk about is when the device goes into a sleep mode and there is absolutely no other way out but by pressing the internal reset. This is also called a kernel panic.
We are always talking about roms on Bootloader 1.2 unless specified.
When installing or removing things from the system, it is always a good idea to reset and clean the cache, clean the dalvik cache and fix permissions.
USB problems sometimes are caused by your own computer, you may have to restart/change USB port/change USB cables/check your USB drivers
Windows 7 is the implied OS most are working on, if you have different then ask.
IF I'M MISSING SOMETHING PLEASE LET ME KNOW
Stuff that WILL cause a SOD (sleep of death) causing you to push the internal reset
DON'T DO THESE
If you plug in USB while your tablet is asleep you will have a SOD
If you do get a SOD please do this so the developers can help.
Use the reset button
Don't power the tablet off at all, just use the internal reset button
Don't touch the tab or do anything but logging into adb.
If for some reason you can't open adb, you can use terminal on the rom
At the prompt type:
Code:
su
Hit enter and then
Code:
cat /proc/last_kmsg
If this doesn't work, the easier way is to access it is with a root explorer by going to /proc and then copy last_kmsg to /sdcard (rename to last_kmsg.txt or zip it up in a file).
Copy and paste the results to a paste bin and post the link. If you don't know pastebin then just post the last 10 lines or so.
tlb1961 install guide
Howdy all,
Glad to hear most are having good luck with this newer revision. To those seeing odd issues after install, I would suggest start over from scratch and clean out the gTab prior to reinstall including repartition the internal SDCard. Run the ROM for a bit before installing anything else. If you have a lot of media files on an microSD card then let it sit for a little while. Once the ROM is running smoothly you should then apply the latest the3dman GApps package.
I know it's tempting to try and hang onto old configs and settings, but it will give you a better experience in the long run if all old data is cleared.
Click to expand...
Click to collapse
lyricalpapa installation essentials
Here's some things I do that work for me:
1. Give my tablet time to boot - let G-Mail, Google Maps, and the other apps load in, talk to the mail server, etc. I watch the activity in the "broadcast" symbol and wait for the browser widget to display its bookmarked pages.
2. Follow the dev's install instructions and @serialplague's FAQ - goes without saying.
3. Have Patience - I give the cache driver's balancing and optimising routines time to do their work after I load a ROM, plus any time I add/remove apps or any time I make changes to the settings. Remember this is a Beta Test ROM and not a snapshot image of a fully tested, optimised, and balanced ROM that you would get if you were to buy a new ASUS Transformer or whatever.
4. Use the apps the Dev's gave us with the Beta ROM - I use the Elixir app regularly to check if the CPU and I/O activity levels have dropped down to near 0% for both. I check them after installing my ROM's, etc. (I also now use the Diagnosis app thanks to @oldtimer)
5. Remember the G tablet only has 512M DDR-2 RAM on board and was built to run with a 2.2 Froyo ROM, a cadged 2.6.32 kernel, and slow generic drivers. Google's minimum published specification for a system running Honeycomb or newer is a Nvidia Tegra-2 processor and 1G of RAM. So the challenge is to modify and tune the 2.6.39 kernel drivers and the ICS ROM to live within the available 512M RAM.
6. edit-no longer needed
7. Killing unnecessary apps sometimes frees up enough memory to stop the CPU and I/O churning. But I have to be careful which apps I kill using an app like Advanced Task Accelerator - it can shut down necessary services - although Android will usually restart them automatically (and kick up the CPU and I/O activity while doing so)
8. Remember that Google Apps come with a high overhead price - the standard Viewsonic set-up for the G tablet does not include GAPPs, and it runs very fast. The same for many other tablets that don't have a Tegra-2 and 1G of RAM. Game players might want to experiment with not loading GAPPs. In the past I've done this by downloading all the apps that I was interested in from GAPPs, then copying them all out to my PC using the "adb pull" command ("adb remount" to get in as root). Then I wipe and reload the ROM without GAPPs, and use "adb push" to put the apps in the right directories. Then on my G tablet, I find the apps using Root Explorer and "click" on them to install them.
Lyricalpapa
Click to expand...
Click to collapse
How do I stop my tablet from downloading every app I have ever owned or used from the market when I log into my android account.
I suspect I am doing something wrong because the tablet is very laggy with ICS.
When you first install it will ask you if you want to use your backups, just uncheck that. Or you can let it sit for awhile, 30min to an hour, it sucks but once everything calms down its much better.
Android Keyboard
Good men of this forum,
It seems that with the new ICS rom, I am having issues with my android keyboard. If my tablet is vertical, I have the dialpad-looking keyboard with what seems to be Japanese characters on a few buttons. When my tablet is in the horizontal orientation, the keyboard disappears completely. I have searched the popular forums here and with Google. I'm terribly sorry if I have missed a tip somewhere.
I used the flashing procedure on the TeamDRH website to the letter, and I am no stranger to flashing custom ROMs to android devices. The keyboard continues to work beautifully under Froyo and Gingerbread ROMs, as well as the earliest beta of ICS. I only seem to have an issue with this version of ICS.
I'm also getting frequent Google Apps errors about the services stopping. After signing in with my account, Market crashed and disappeared from my apps menu altogether.
It seems that I have a fairly unique problem. I'm a linux sysadmin and I'm very handy with the command line if you need dmesg or kernel output.
Thank you in advance.
I've heard a couple of people are having problems with the GApps, have you tried installing with the lite 7b GApps?
No Luck
Thanks for the reply!
I have tried both the full and lite versions of 7A and 7B for this ROM with no luck. When I perform a first-time boot of the tablet after a ROM and Gapps, the very first message I encounter is "Unfortunately, the process com.google.process.gapps has stopped" for any version of Gapps, and it continues to pop up every several seconds that the tablet is in use.
I have also tried installing the ROM without Gapps at all and the keyboard is still nowhere to be found. Odd that the keyboard works in the first beta (1E), but this ICS (2B) is much faster than the old one
If anyone has a link to download the ICS Preview 2A instead of 2B I would be interested in trying it out, the links on TeamDRH's website all point to 2B now.
Other useful info: I know for certain that I am running the 1.2 bootloader and I'm using the newest Clockworkmod v5.5.0.4 Beta 15. I like to re-format before every flash to ensure a clean start.
Thats very odd it sounds like the download may have been corrupted. I've seen it happen a couple of people.
I still have 2A and some previous ones, kinda a catalog lol, just PM if you want to go that way.
I'm a newb
Thank you very much for the help you've provided me.
I tried downloading 2B a few more times with the same issue :/ so strange. Unfortunately for me, I am below the 10 post minimum to allow PMs. It's kind of ironic actually, I've been a member for years and always found my answers without having to ask because xda is wonderful about providing info
Thanks again.
Sent ya an email
simplyphp has a great writeup on an installation method you could try his way
SUCCESS!
Using the simplyphp method you referred me to, not only does the 2A ROM work, but the newest ROM and Gapps as well! I must admit that I'm a little embarrassed that I can't actually identify the original problem, but I believe it has something to do with my installation of Clockworkmod. I got it from a forum here that is trustworthy, but it didn't seem to work exactly as I needed it until I installed it with nvflash. I also had a strange problem with the first flash (out of the two that I am supposed to do) in that it wouldn't boot all the way into the TnT factory OS and was in an endless reboot. I simply turned it off, booted into APX mode once again, and continued with the listed steps and it worked flawlessly. I would thank simplyphp but I can't post on development threads yet!
So thank you and have a "Thanks!", I hope I've contributed to your wealth of knowledge on troubleshooting.
i just got my note pro 12.2 wifi version (international) a few days ago and already experiencing problems, firstly the wifi was so slow so i updated it OTA to the latest stock firmware i can't remember what it is but it's the latest official 4.4.2 they have and that improved the wifi but now i'm encountering issues of rebooting randomly after using facebook app. it's always after i lock the screen it suddenly reboots after 2 mins or something especially if i have say been using a lot of memory for it.. ie if i scroll down 4000 friends that's when it always reboots once i lock the screen. is this liekly to be hardware or software issue or an app issue?
i have only had it a few days so haven't managed to play with it enough to test it to the max.
just now it rebooted and i played one youtube HD video and used multi window to use the facebook app (old version 7.0 - i like this version).. but i hadn't used the facebook app that much while on, the only thing i did different was i plugged in my samsung s3 charger into the note pro to test how long it would take to charge using a usb 2.0 connection instead. it's official charger official cable, is that likely to cause reboot issues?
previously it was just after using facebook for a long time for a ram intensive amount, i also tested it after reboot and using facebook a bit and locking screen and it didn't reboot so it made me think ok it's just when facebook is being used a lot and all the ram and memory is exhausted caching 4000 friends viewing so i didn't think anything of it.
is this likely to be hardware or software issue? are hardware issues ever the main problem with rebooting?
I know the usual tests, having to use odin to flash official firmware, trying a different facebook version, removing and not using facebook at all and see if it still reboots and lastly factory reset.
ideally i'd like to avoid all of those things as it is a major hassle and i can live with the reboot issue provided it isn't a hardware problem. is there anyway to test it to know for certain it is hardware and not software and the app?
edit: it keeps rebooting even if i dont use the app
seems to happen when i lock the screen sometimes it just reboots randomly.
anyone else have this?
You could try to remove that facebook app and see if that fixes the problem.
does anyone know what is causing this?? is it hardware?
i've factory reset removed all apps, then added one app at a time then added about 6gb of videos and added wakelock detector. all seemed fine
then i tried to unmount the sd card and then it rebooted.. why is it doing this??
pete101 said:
does anyone know what is causing this?? is it hardware?
i've factory reset removed all apps, then added one app at a time then added about 6gb of videos and added wakelock detector. all seemed fine
then i tried to unmount the sd card and then it rebooted.. why is it doing this??
Click to expand...
Click to collapse
Could it be a bad sector on the SD card? I'd long format it using a pc to be sure.
Sent from my SM-P900 using Tapatalk
it's not the faceboook k app i've realised now it just coincidentally seemed to be that as it is ram intensive.
i factory reseted and then put the app back on but didn't log in. 3 times it has rebooted by itself over different scenarios.. 1 plugging in a samsung usb 2.0 charger from a samsung s3, 2 when unmounting sd card, 3 when closing the screen when any ram intensive app is in the background (there's still like 500mb of ram left!! i dont know why it's rebooting like this.
i can't figure it out. is anyone else having these issues? im not sure if it's a kitkat 4.4.2 issue.. reading forums from other users with different devices i'm seeing the reboot issue coming up alot especially on the s4.
http://forum.xda-developers.com/xposed/modules/samsung-kitkat-systemserver-crash-fix-t2806046/page22
but i dont know for certain if it's a hardware issue.
my next steps which i really want to avoid is to factory reset AGAIN and not load any apps (the problem with this is it requires a certain amount of ram intensity to be used before it randomly happens.. if i dont add any apps like instagram or facebook or tumblr i can't get it back to the state where it reboots randomly)
i've also enabled all apps (i usually disable all the bloatware i can without being rooted) but it does bring up errors of android.core.process has stopped etc and some gapps errors (im hoping this is the cause of the reboot) and see if it reboots. it's difficult recreating the scenario consistently.
i udnerstand it might reboot if you've overused the memory but it clearly shows lots is free so i can't figure out what is causing it?
my next step after all this is to flash the latest version of stock so i can't put it down to the OTA updates that is causing it. if that fails i revert to odin to flash the original 4.4.2 it came with.. and failing that i'll have to return it
does anyone have any ideas whether it is hardware (maybe the power button is slightly off so when you press down it in a certain angle it triggers a restart?)
or is the motherboard or corrupted sector of the memory which when it writes over it causes the reboot?
i always assumed reboot issues were normally always firmware issues and not hardware.. surely samsungs quality control is a bit better than that??
If it were me I would yank the microsd card out, factory reset, set up just my gmail without allowing auto backup/restore and apply all updates. I'd then let the tablet run for a full day and use it just for web browsing and Youtube to see if the problem is still there. I would not install anything for at least a day, including the microsd card. This would be as stock as one could get and rule out the possibility of it being any software that I installed or the microsd that I was using.
I suspect it's software but the only way to know is to be patient and test it out for sure.
Sent from my SM-P900 using Tapatalk
Hi,
same tablet, bought there is 3 weeks. I installed the latest firmware update (XXUANI1)
I rooted the tablet (to allow sd-card writing).
and that's it.
like some of you, I have random reboot.
I can't remember if it happened before the root or not. I think that yes, but I am not 100% sure.
I don't see anyone reported that the root cause random reboot...
it is really random. sometime, the tablet stay one night without reboot, sometime, I can have 3 reboot in one hour.
I don't find what kind of application is causing that issue.
I really believe that it is software. before the firmware update, I stayed 2 weeks without any issue.
I tried to reboot in recovery mode, and wipe the cache, without success.
I will probably try to do a factory reset...
Olivier
orobin said:
Hi,
same tablet, bought there is 3 weeks. I installed the latest firmware update (XXUANI1)
I rooted the tablet (to allow sd-card writing).
and that's it.
like some of you, I have random reboot.
I can't remember if it happened before the root or not. I think that yes, but I am not 100% sure.
I don't see anyone reported that the root cause random reboot...
it is really random. sometime, the tablet stay one night without reboot, sometime, I can have 3 reboot in one hour.
I don't find what kind of application is causing that issue.
I really believe that it is software. before the firmware update, I stayed 2 weeks without any issue.
I tried to reboot in recovery mode, and wipe the cache, without success.
I will probably try to do a factory reset...
Olivier
Click to expand...
Click to collapse
Assuming you have custom recovery installed as well; have you tried wiping dalvic? It will force applications to recompile and possibly fix a corrupted application or its associated files.
Hi,
I just checke.…
I was thinking that the root method was not setting the knox flag, so i was thinking there is no recovery in the file flashed… .
I was wrong.
My waranty is void, knox is set. I still have no custom recovery : in the file provided by chainfire, there is a recovery which is probably coming from samsunG…
So i will install a new recovery and try to wipe all caches dalvik.etc.
Hi,
since my knox is set now :
I tried to install TWRP recovery, which allow me to do a wipe of the cache AND dalvik Cache.
it did not resolved anything. the tablet still reboots randomly.
then, I decided to restart from scratch :
I flashed the same firmware I had, using ODIN, and do not root it.
this is this firmware : http://www.sammobile.com/firmwares/database/SM-P900/XEF/
I will keep you updated if it solve the reboot issue or not.
thanks
Olivier
pete101 said:
i always assumed reboot issues were normally always firmware issues and not hardware.. surely samsungs quality control is a bit better than that??
Click to expand...
Click to collapse
Hi
I had the same problem and also thought it was the power button that was faulty but then I flashed the previous firmware then tried to use it a bit and no reboots since so I guess samsung released a new firmware that solved the slow wifi problem but then boosted it a little too much or so it seems judging by the reboots whenever there's too much overload.
So I guess for now I will stick with an older firmware
oops... it rebooted while I was surfing the play store so I guess I spoke too soon
Im new to all this so pay no attention if its nonsence...
My S5 G900f has a qualcomm snapdragon chipset, that doesn't support monitor mode, which i believe means that it doesnt support packet injections or packet capturing (driver related?)
using the dsploit.apk for things like session hijacking, replacing web page images of a target and using script 'injection' to inject custom java script into a target web page, all sounds like things you'd need monitor mode to do. and if it is then i was able to do it with my S5.
I dont know a lot about coding or how it all fits together and communicates with the hardware, so i may sound completely stupid, but this has done my head in for ages, so why not get it out there.
1. when i attempted to upgrade from my first custom rom, i had a bit of trouble, softbricked my phone and then flashed the two roms in various, alternate, wipe, format and install combinations until it finally booted to set up, and i stopped panicking. but this caused features from the first rom to appear within the second rom.
ie: 3minute battery mod was installed through a add-on zip along with the first rom and nothing to do with the second at all.
2. inconsistencies within the file system, like file names that were apps included with the first rom.
3. dsploit.apk was bugged and crashed every 5 or 10 minutes. then would seem to glitch or stutter for a couple seconds before correcting its self and accomplishing its pen test.
4. i also remember watching green text in the terminal as it failed to connect or ID some part of the system but continued to retry in quick succession until it glitched and worked. (i think this was a similar type of app i was trying out at the same time but instead of GUI stutters, i could see the text rapidly stuttering and glitching.)
4. the dsploit.apk worked for me back then, even though it was temperamental. ive downloaded the apk a couple times since with various roms and ive got no where with it...
was thinking maybe different aspects of the two roms had been filed or grouped together and created unstable triggers within the software, allowing it to briefly communicate with the chipset. i may be way off, but ive been sat here waiting for someone to solve this issue forever, i thought id share my thoughts, on the off chance it turns out to be something and i can finally get my S5 into monitor mode without OTG cables and other unwanted auxiliary components.
thanks in advance
G Carter
Do a clean install of you ROM, and please, don't panick. If you want to have a good time flashing ROMs and stuff, panicking is the last thing you want to do, it will cause stress and stress can lead to not being careful enough so stuff like this happens, well, always, if you are experiencing issues do a clean install. Just boot into recovery (I recommend TWRP) and wipe everything except external sd. Open ADB and sideload the ROM (or, if you have enough memory on a flash drive, plug it into your android and flash it from there) and then Google Apps.
I picked up an Mi 4 a bit over a year ago to test Windows Mobile as the organization was evaluating the ecosystem then.
There wasn't enough interest in it so the phone sat in a drawer for several months.
Wanting to breathe new life into the device, I made the switch back to Android this morning via MIUI 8 without issue.
Then I learned LineageOS was available for it so I laid that down:
Got TWRP setup per https://twrp.me/devices/xiaomimi3.html & https://wiki.lineageos.org/devices/cancro/install
Got LineageOS installed per https://wiki.lineageos.org/devices/cancro/install
At the same time, installed the nano variant of OpenGApps http://opengapps.org/?api=7.1&variant=nano
Everything went off error free and the phone booted just fine.
But after getting it all setup, I started seeing several notifications that various apps won't work until Google Play Services is installed. When I tap on the notification, a window briefly launches then disappears just as fast. I assume it was the Play Store but it can't be certain because its essentially a blank window that appears for less than a second without fully drawing/rendering the content within. When I click on the Play Store, it won't open at all, often not even displaying anything (even momentarily) on screen like the tap on the notification does.
I booted back into TWRP, re-applied the same nano variant but that didn't help.
Thinking I made a mistake somewhere, I started over by wiping and reinstalling the OS, downloading & pushing a fresh download of the nano variant package yet the problem persisted.
After the second installation I decided to try with the super and stock variants but both failed due to not enough space on /system.
I'm in transit at the moment so I'll give it another go with the mini then micro variants later, but wanted to get this out there in the event someone could point out what I might be doing wrong.
Thanks in advance.
Solved - Use Mini Variant
I applied the mini variant and all is well.
So I have to ask the question: Was what I experienced to be expected? If not, what might I have done wrong?
Install disk info and post a screenshot here
You system partition should be 1.2 gb.
Sent from my Mi 4 using XDA Labs
Hey, guys. Maybe you have been following this:
https://www.reddit.com/r/GooglePixe...r_saving_mode_turning_itself/?sort=confidence
Google confirmed, that the can activate the battery saver from their and accidentally had the test group set to big. A lot of devices over the whole range had the problem. And I suspect it made mine bootloop:
I was helping friends of family get their internet connection up and running around that time. I once used my bacon to check for the SSIDs in the area and then didn't touch it anymore, until the job was done approx 2 hrs later. So I pulled out my bacon and it was at the part, where I should enter the encryption password. No biggie, I though. Random reboots occur when you ROM. Entered the password only to have it boot for ages and finally bringing me to TWRP with "Rescue Party" tag. Up until now I didn't get it up and running. I flashed substratum rescue, removed every magisk module and then magisk alltogether. It still does not boot but brings me back to TWRP. I will try dirty flashing in order to get back into the device and securing everything again before factory resetting it. I hope that will be the end of it.
Anyway: i have a bacon running the latest LOS. Anybody experience something similar? Or would you consider this all to be a coincidence? Timing wise it'd fit perfectly to above battery saver issue. I'm taken aback, that something relatively harmless like activating the battery saver at the same time was a kill switch for my device. I was always confident enough to have a rooted and ROMed phone as my daily driver. But if this can happen, what else could?
device: bacon
ROM: latest LineageOS
rooted: yes (Magisk)