Related
Hi all,
I have a t-mobile phone and tried to install android 2.2. there. I used mdeejay's and darkStone's builds, but wifi didn't work at any of them. I've found a person who uses T-mobile hd2 too and installed the same versions of rom and radio. It didn't helped. In windows mobile wifi works well.
Could you please advice how to hande it? Did anyone face the same problem?
Thank you in advance.
#did some debug via adb:
I suppose that the red line below tells about reason.. But I haven't dealt with WPA on android before.. Any help is appreciated.
D/WifiService( 1916): setWifiEnabled( mAirplaneModeOverwridden=)false
I/WifiHW ( 1916): wifi_load_driver enter
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = false
I/WifiHW ( 1916): wifi_load_driver end right 3
I/WifiHW ( 1916): wifi_start_supplicant enter
I/WifiHW ( 1916): wifi_start_supplicant end right 2
D/WifiService( 1916): ACTION_BATTERY_CHANGED pluggedType: 2
I/wpa_supplicant( 2771): CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00
:00:00
E/wpa_supplicant( 2771): Failed to disable WPA in the driver.
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = true
D/PowerManagerService( 1916): New lightsensor value:40, lcdValue:90
D/lights ( 1916): set_light_buttons
D/lights ( 1916): set_light_keyboard
E/SettingsWifiLayer( 2298): Unable to scan for networks
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x6257a8), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x6257a8), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::requestBuffer(this=0x6257a8), index=0, pid=2298,
w=350, h=85 success
E/WifiHW ( 1916): Supplicant not running, cannot connect
E/SettingsWifiLayer( 2298): Unable to scan for networks
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x4ca268), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x4ca268), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::requestBuffer(this=0x4ca268), index=0, pid=2298
w=350, h=85 success
E/WifiHW ( 1916): Supplicant not running, cannot connect
V/WifiStateTracker( 1916): Supplicant died unexpectedly
D/WifiStateTracker( 1916): Reset connections and stopping DHCP
D/NetUtils( 1916): ifc_get_info addr=0 !
D/WifiStateTracker( 1916): Disabling interface
D/WifiService( 1916): setWifiEnabled( mAirplaneModeOverwridden=)false
D/WifiStateTracker( 1916): Reset connections and stopping DHCP
D/NetUtils( 1916): ifc_get_info addr=0 !
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = true
D/WifiStateTracker( 1916): Disabling interface
I/WifiHW ( 1916): wifi_stop_supplicant enter
I/WifiHW ( 1916): wifi_stop_supplicant end right 1
I/WifiHW ( 1916): wifi_unload_driver enter
I/WifiHW ( 1916): wifi_unload_driver end right 2
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = false
how to set up MAC address for android builds (except startup.txt)?
Hi again,
I did some search and found that the core of the problem is in getting MAC address for wifi. (as dmsg says). Exactly the same problem was for Touch2, Tilt and other devices (http://forum.xda-developers.com/showthread.php?p=9211659) and it was resolved after they corrected wifi-nvram.txt. This file is responsible for setting up MAC address there, but I couldn't find it at builds for hd2.
if anybody knows what file is used to set up MAC address for wifi, I would be very appreciated.
Thanks!
I believe they just checked for their WiFi mac address from one of the following locations:
Settings->About phone->Status
Wireless & Networks -> WiFi Settings -> Menu Button -> Advanced
Then they edited the nvram.txt file @ /system/lib/hw/wifi/nvram.txt to include the proper MAC address.
Thanks for the answer!
Unfortunatelly wireless settings are not available until wifi is turned on.
I investigated the problem deeper and found that the reason could be in wifi hardware initialization. I did dmesg and saw the following:
wlan: wifi_set_power = 1
htcleo_wifi_power: 1
wlan: wifi_set_carddetect = 1
htcleo_wifi_set_carddetect: 1
mmc0: card_present 1
mmc0: Slot status change detected (0 -> 1)
wlan: Dongle Host Driver, version 4.218.204.2
mmc0: queuing CIS tuple 0x91 length 3
mmc0: new high speed SDIO card at address 0001
wlan: DHD: dongle ram size is set to 294912(orig 294912)
wlan: dhd_bus_rxctl: resumed on timeout
wlan: firmware version: ver
wlan: Return_dpc value is : 0
wlan: stop poll
wlan: dhd_bus_rxctl: resumed on timeout
wlan: dhd_preinit_ioctls: can't get MAC address , error=-110
wlan: dhdsdio_probe: failed
Since in windows mobile wifi does work I used the firmware files from WM: nvram.txt and rtecdc1.bin. As it turned out nvram in android is located in /proc/calibraion. But unfortunatelly it didn't help. So, I think that the problem is in bcm4329.ko driver. I'm not sure why other people with the same hd2 (t-mobile US) and the same ROM/RADIO/Android have no such issue. Perhaps my broadcomm hardware has a problem which is bypassed in windows, but not in Android.
I wonder if there is a way to get more detailed info than dmesg and logcat give (except building andoid sources of course ).
I don't know if it can help, but still, I'll say it anyway.
I think i had the same problem some times ago.
Wifi in android wouln't work, but was perfectly working in winmo.
it seems that if wifi is on in winmo when you boot on android, the wifi device seems to be blocked in some way.
Do you have wifi enabled in winmo? if yes, try to disable it, and boot on android to see if it works.
Hi kushulain,
Thanks for the advice! (I've almost started to build andriod by myself to find out the reason..) Unfortunatelly wifi was turned off when android was booting.
But this is another point to play around. I haven't tried to boot andriod with wifi turned on.
Thanks!
Just tried to boot andriod with wifi turned on. The device hangs at the beginning of the booting (even before screen with 'htc' appears). I think it is connected to my problem.
Did someone have similar problems?
Hey, I have the same problem, did you find any solution ?
Guys have you tried to change the radio part of the phone with a suitable one?
canavaro said:
Hey, I have the same problem, did you find any solution ?
Click to expand...
Click to collapse
hi, I didn't fix it actually due to lack of time. I tried to use wm hw init files in Android, but it didn't help. There is a score of my posts on this forum regarding this topic so you can find exactly what I tried. The funny thing is that WiFi works in wp7.
To stealth21
yes, that was the first thing I tried.
RAZR XT710 EU
I've had spotty GPS functionality ever since I've switched to the CM10.1 roms which means I had to sometimes restart the phone to get the blinking status icon. But once it was blinking I knew it took a few seconds to lock and I would get some satellites even indoors.
Two weeks ago the GPS stopped working completely, ever since I removed the SIM card. I've tried reinstalling the same ROM, installing other ROMs, doing a clean install on another slot (4.1.2. SPREM) but it just does not want to find any satellites.
I've used GPS Toolbox, Faster GPS and NMEA Decoder to see what it's outputting. On one ROM I was getting some strings with $PMOTO but no NMEA position strings.
The libgps shows an error code which could be either 9 on one ROM or 12 on another:
Code:
D/libgps_GpsMgr( 444): schedGps() mode: 3, tbf: 0, accuracy: 0, perf: 0, pAgps: null
D/libgps ( 444): GpsInterface_stop()
E/libgps ( 444): recv_command_status() : fix returned error code 9
D/libgps_GpsMgr( 444): sched() set mode: 3, tbf: 0
D/libgps ( 444): status_cb: GPS_STATUS_SESSION_END (2)
D/libgps_GpsMgr( 444): schedGps() mode: 0, tbf: 1, accuracy: 0, perf: 0, pAgps: null
D/libgps ( 444): GpsInterface_set_position_mode( 0, 1, 100, 0 )
D/libgps ( 444): GpsInterface_start()
D/libgps_GpsMgr( 444): sched() set mode: 0, tbf: 1
D/GpsLocationProvider( 444): NTP server returned: 1382386872254 (Mon Oct 21 22:21:12 CEST 2013) reference: 36370 certainty: 18 sy
stem time offset: -326353
D/libgps ( 444): GpsInterface_inject_time( 1382386872254, 36370, 18 )
D/libgps ( 444): status_cb: GPS_STATUS_SESSION_BEGIN (1)
V/PhoneStatusBar( 576): setLightsOn(true)
D/libgps ( 444): GpsXtraInterface_inject_xtra_data( 0x41FC6370, 60862 )
......
E/libgps ( 444): recv_command_status() : fix returned error code 12
AFAIK the GPS functionality is on the same chip with WiFi and Bluetooth, both of which work perfectly. Is there any antenna connector that might have come loose? I didn't see any in the ifixit teardown.
Can Matt's utility be used to reset a phone that's non-Verizon? Or should I use RSD?
Fixed by flashing the factory firmware with RSD Lite.
Hi,
I also had a problem with GPS in Russia,
Here is a solution what helped me.
http://forum.xda-developers.com/showthread.php?p=43910953
If you don'thave the gps.omap4.so file, just placed the attached file on system/lib/hw, fix permissions (RWX / R-- / R--) via any root file explorer and reboot.
Click to expand...
Click to collapse
Hello,
recently I get my Teclast X89 tablet, but unfortunately it appeares to have a problem. When the battery charging level comes to 100% (at 99% everything is OK) tablet becomes totally unusable. When the screen is switched off it cannot be waken up and when I use the tablet a window pops up telling that "Process com.android.systemui has stopped", like here:
imgur.com/hjWI1lP
After restart everything is OK, but it really grinds my gears. Maybe someone know how to fix this problem?
Please halp!
Bogusz
Go to developer settings and enable android debugging. Now connect to computer set up adb drivers and post a logcat at the time of crash
MasterAwesome said:
Go to developer settings and enable android debugging. Now connect to computer set up adb drivers and post a logcat at the time of crash
Click to expand...
Click to collapse
Hello again,
I've made logcat, here is an interesting part, I think:
I/SecurityManagerService( 671): SMS received security event: App[START/com.android.keyguard]
I/WindowState( 556): WIN DEATH: Window{26a85ad0 u0 Keyguard}
I/ActivityManager( 556): Process com.android.systemui (pid 622) has died.
W/ActivityManager( 556): Scheduling restart of crashed service com.android.systemui/.SystemUIService in 0ms
W/ActivityManager( 556): Scheduling restart of crashed service com.android.keyguard/.KeyguardService in 0ms
D/InputMethodManagerService( 556): --- calledFromForegroundUserOrSystemProcess ? calling uid = 1000 system uid = 1000 calling userId = 0, foreground user id = 0, calling pid = 556dalvik.system.NativeStart.run(Native Method)
W/ActivityManager( 556): Scheduling restart of crashed service com.android.systemui/.ImageWallpaper in 0ms
I/StatusBarManagerService( 556): binder died for pkg=com.android.keyguard
I/WindowState( 556): WIN DEATH: Window{269b48a8 u0 NavigationBar}
W/InputDispatcher( 556): Attempted to unregister already unregistered input channel '268ba8e8 StatusBar (server)'
D/dalvikvm( 3948): Try to disable coredump for pid 3948
D/dalvikvm( 3948): Process 3948 nice name: com.android.systemui
D/dalvikvm( 3948): Extra Options: not specified
Click to expand...
Click to collapse
I discovered also that when the battery level drops to 99% process starts to work properly.
I include also whole log file compressed to .zip.
Still need help!
I have the same problem, even after a factory reset.
me too having the same issue. Is it hardware failure or just android?
I found a solution in an other tread :
http://forum.xda-developers.com/android/general/review-teclast-x89-baytrail-tablet-dual-t3039961
Hi all,
I am using modpunks CM 12.1 on my G850F.
Working very nice. Now I get the following problem(s):
Random freezes, if I get freezings, very regular I cannot switch on the phone instantly. It's draining battery but I cannot boot it (no samsung logo...) nor I cannot boot into recovery. Only download mode works sometimes.
The SAME happens with stock ROM. Tried the "old" frenche XEF version, the "new" one from late november and the one the phone was initially delivered with.
To me it seems kind of if there is either a memory problem OR a CPU problem especially as I only get this problems when using the phone. so I can keep it in my pocket and it works.
Do you have other ideas howto narrow the problem down? Up to now there is no clear variant how to reproduce this behavior. but it happens now very often and EVEN when restoring CM from recovery once.
Best and thanks for your ideas and help,
Blubberor
I would suggest testing with some benchmark app. If it crashes take notice when it did. If not make a clean flash with odin with repertition ticked ON and see if it repeats the error.
Sent from my P6-U06
Same issue
Hi. I have the same issue with my Alpha. Official room, tried to reset several times with no result. It gets hot and then freezes. A friend of mine has same phone and OS version, no freezes encountered. Waiting for an update from Samsung.
Blubberor said:
Hi all,
I am using modpunks CM 12.1 on my G850F.
Working very nice. Now I get the following problem(s):
Random freezes, if I get freezings, very regular I cannot switch on the phone instantly. It's draining battery but I cannot boot it (no samsung logo...) nor I cannot boot into recovery. Only download mode works sometimes.
The SAME happens with stock ROM. Tried the "old" frenche XEF version, the "new" one from late november and the one the phone was initially delivered with.
To me it seems kind of if there is either a memory problem OR a CPU problem especially as I only get this problems when using the phone. so I can keep it in my pocket and it works.
Do you have other ideas howto narrow the problem down? Up to now there is no clear variant how to reproduce this behavior. but it happens now very often and EVEN when restoring CM from recovery once.
Best and thanks for your ideas and help,
Blubberor
Click to expand...
Click to collapse
flc555 said:
Hi. I have the same issue with my Alpha. Official room, tried to reset several times with no result. It gets hot and then freezes. A friend of mine has same phone and OS version, no freezes encountered. Waiting for an update from Samsung.
Click to expand...
Click to collapse
my wife as well.
although I have to admit, mine had to go 3 times to Samsung CSC, while hers is just working fine.
This is just a strange happening.
will do two things. soon.
Complete erase of all files.
Will open the phone to check if I see something strange...
In case I can get it back to work I will report back.
Best,
Blubberor
Why is it no matter what i post on XDA people just ignore it wut
now its official.
Odin was not able to repartition only regular flashing..., while completely opening in the end the display broke.
so I loved this phone, but as it made problems all over the time (even before testing and using CM (thx @modpunk ones again!!!)) won't stick to samsung.
now first use the good old nexus 4....
best and thanks to all from the samsung alpha area here on xda!!
was lucky...had the phone connected to adb and logcat was running when it crashed.
maybe someone can have a look. to me there is nothing strange on the system going on...
I have checked with E2FSCK memory and integrity of SYSTEM, DATA, EFS....partition without any strange error reports..
I was wondering if one can fully check the whole memory to exclude just bad blocks.
right now the phone was just charging when I unlocked screen and was starting logcat---
Code:
01-03 16:25:04.882 10126 10126 W GAv4 : AnalyticsReceiver is not registered or is disabled. Register the receiver for reliable dispatching on non-Google Play devices. See http://goo.gl/8Rd3yj for instructions.
01-03 16:25:04.886 10126 10126 W GAv4 : CampaignTrackingReceiver is not registered, not exported or is disabled. Installation campaign tracking is not possible. See http://goo.gl/8Rd3yj for instructions.
01-03 16:25:04.891 10126 10163 W GAv4 : AnalyticsService not registered in the app manifest. Hits might not be delivered reliably. See http://goo.gl/8Rd3yj for instructions.
01-03 16:25:04.990 2865 5470 I ActivityManager: Start proc 10164:com.estrongs.android.pop/u0a160 for broadcast com.estrongs.android.pop/.app.StartServiceReceiver
01-03 16:25:05.003 2865 3167 I ActivityManager: Killing 9510:com.android.deskclock/u0a39 (adj 15): empty #17
01-03 16:25:05.264 2457 2457 D gpsd : WakeLock(Acquire,GPSD)
01-03 16:25:05.264 2457 2457 D gpsd : WakeLock(Release,GPSD)
01-03 16:25:05.277 2865 3106 D WifiService: releaseWifiLockLocked: WifiLock{NlpWifiLock type=2 [email protected]}
01-03 16:25:05.361 3066 10110 I SecHAL : device_sleep: NFC can be going to sleep
01-03 16:25:05.405 4517 4630 I GCoreUlr: Successfully inserted 3 locations
01-03 16:25:05.409 4517 4630 I GCoreUlr: Starting service, intent=Intent { act=com.google.android.location.reporting.UPLOAD cmp=com.google.android.gms/com.google.android.location.reporting.service.DispatchingService }, extras=null
01-03 16:25:05.416 10164 10184 W ResourceType: No package identifier when getting value for resource number 0x00000000
01-03 16:25:05.421 2865 2979 D WifiService: New client listening to asynchronous messages
01-03 16:25:05.495 2865 3622 I ActivityManager: Killing 8291:com.cyanogenmod.lockclock/u0a53 (adj 15): empty #17
01-03 16:25:05.893 4517 10195 W BaseAppContext: Using Auth Proxy for data requests.
01-03 16:25:05.917 4517 4517 V GLSActivity: AuthDelegateWrapperCreated with selected intent: Intent { cmp=com.google.android.gms/.auth.DefaultAuthDelegateService }
01-03 16:25:05.925 4517 4517 V GLSActivity: AuthDelegateWrapperCreated with selected intent: Intent { cmp=com.google.android.gms/.auth.DefaultAuthDelegateService }
01-03 16:25:06.218 4517 4525 E DataBuffer: Internal data leak within a DataBuffer object detected! Be sure to explicitly call release() on all DataBuffer extending objects when you are done with them. (internal object: [email protected])
01-03 16:25:06.220 4517 4525 E DataBuffer: Internal data leak within a DataBuffer object detected! Be sure to explicitly call release() on all DataBuffer extending objects when you are done with them. (internal object: [email protected])
01-03 16:25:06.222 4517 4525 E DataBuffer: Internal data leak within a DataBuffer object detected! Be sure to explicitly call release() on all DataBuffer extending objects when you are done with them. (internal object: [email protected])
01-03 16:25:06.224 4517 4525 E DataBuffer: Internal data leak within a DataBuffer object detected! Be sure to explicitly call release() on all DataBuffer extending objects when you are done with them. (internal object: [email protected])
01-03 16:25:06.226 4517 4525 E DataBuffer: Internal data leak within a DataBuffer object detected! Be sure to explicitly call release() on all DataBuffer extending objects when you are done with them. (internal object: [email protected])
01-03 16:25:06.255 2865 5101 D NetlinkSocketObserver: NeighborEvent{elapsedMs=382899, fd00::9ec7:a6ff:fe12:55e6, [9CC7A61255E6], RTM_NEWNEIGH, NUD_REACHABLE}
01-03 16:25:06.705 2865 2980 D ConnectivityService: notifyType CAP_CHANGED for NetworkAgentInfo [WIFI () - 100]
01-03 16:25:06.730 4517 10195 I GCoreUlr: Batch Location Update succeeded for account account#-16#
01-03 16:25:06.767 4517 10195 I GCoreUlr: Upload task finished
01-03 16:25:06.770 2865 2876 W AppOps : Finishing op nesting under-run: uid 10012 pkg com.google.android.gms code 40 time=1451834705429 duration=97 nesting=0
01-03 16:25:06.819 2451 2899 V audio_hw_primary: do_out_standby: output standby: 0
01-03 16:25:06.877 3012 3012 D PhoneStatusBar: disable: < expand ICONS* alerts SYSTEM_INFO* back home recent clock search quick_settings >
01-03 16:25:08.695 2451 2899 V audio_hw_primary: out_set_parameters: key value pairs: routing=2
01-03 16:25:08.698 9786 9786 W System : ClassLoader referenced unknown path: /system/framework/tcmclient.jar
01-03 16:25:08.706 2451 2899 V audio_hw_primary: start_output_stream: starting stream
01-03 16:25:08.709 2451 2899 V audio_hw_primary: *** select_devices: Routing hasn't changed, leaving function.
01-03 16:25:08.709 2451 2899 V audio_hw_primary: start_output_stream: stream out device: 2, actual: 2
Blubberor said:
was lucky...had the phone connected to adb and logcat was running when it crashed.
maybe someone can have a look. to me there is nothing strange on the system going on...
I have checked with E2FSCK memory and integrity of SYSTEM, DATA, EFS....partition without any strange error reports..
I was wondering if one can fully check the whole memory to exclude just bad blocks.
right now the phone was just charging when I unlocked screen and was starting logcat---
Code:
01-03 16:25:04.882 10126 10126 W GAv4 : AnalyticsReceiver is not registerэ...
Click to expand...
Click to collapse
I'll help you. Turn the unlocking fingerprint.
What does this mean exactly?
Still have freezings. Kind of desperate how to brick the device..
Sent from my Nexus 4 using XDA Free mobile app
Turn off unlocking fingerprint.
Volks.com.ua said:
Turn off unlocking fingerprint.
Click to expand...
Click to collapse
would even be not supported in CM13 so there is no option I guess.
Thanks already - fingerprint was already exchanged and broken again bei CSP some months ago....
Best,
Blubberor
Hi! My cellphone has the same problem. Please, let me know if you could solve it.
Thanks,
Pablo
pablitolandia said:
Hi! My cellphone has the same problem. Please, let me know if you could solve it.
Thanks,
Pablo
Click to expand...
Click to collapse
Unfortunately could not solve it.
No errors in file checks, efs restored....Samsung refused warranaty due to Knox. Today a used alpha that I bought is going to arrive.
Good luck.
Blubberor
Sent from my Nexus 4 using XDA Free mobile app
Hi all, a quick fix that worked for me was to use another launcher.
nickps17 said:
Hi all, a quick fix that worked for me was to use another launcher.
Click to expand...
Click to collapse
To me happened with Stock as well as with cm.
Crossing the fingers for you.
Sent from my SM-G850F using XDA Free mobile app
CD Switcher requires [root].
{
"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"
}
If you are into IT or cautious or ever had a drive die, you know that sometimes you can't trust a hard drive. Need to resize a partition but can't do it while the system is running? Want a clean virus scan? We all need a good boot disk sometimes and now you can carry a bunch on your phone !
Like DriveDroid and similar products, this uses the gadget driver in the Linux kernel. This updated version should work on more devices and custom ROMs, but has had very little testing. It's Alpha-ware and I'll add more features later.
Install CD Switcher APK (yes, I wrote it) from here:
https://drive.google.com/file/d/1ZdSYIhs7pq8IrOZ4NBX4dzPSYP5tdeIh/view?usp=drivesdk
Now tap on any ISO file. It can be inside an email or on the web and it will download it. (Unfortunately, this is how it works with the OOS file manager, meaning it makes an extra copy, so using FX, pictured, is recommended). The system will ask how to open it. Select CD switcher and 'Always' and grant root when it asks.
The DriveDroid APK doesn't work on stock OOS. I've booted many CDs with this tool. You can change CDs with just a tap. Have fun with your 128GB!
EDIT: New version using better methods doesn't rely on OOS init.
Sweet! I have always wanted to be able to do this but I have not been able to ever get drivedroid to work! I can't wait to try it out and not have to carry around more than my phone and a usb cable
knightrider64 said:
Sweet! I have always wanted to be able to do this but I have not been able to ever get drivedroid to work! I can't wait to try it out and not have to carry around more than my phone and a usb cable
Click to expand...
Click to collapse
I've heard drivedroid works with other kernels but the UI is a nightmare so I would still rather use this. Let me know if you have any issues with it.
Sent from my ONEPLUS A3000 using Tapatalk
Great app, works fine. But how do you umount the iso?
Any chance to get vhd's to work? I have an external hard drive that boots CDs and vhd's. Would be great to have it all on my phone :good:
thomas_pieps said:
Great app, works fine. But how do you umount the iso?
Click to expand...
Click to collapse
You can't. Not really any need to since it mounts read only. You can unplug it at any time.
Sent from my ONEPLUS A3000 using Tapatalk
domsch1988 said:
Any chance to get vhd's to work? I have an external hard drive that boots CDs and vhd's. Would be great to have it all on my phone :good:
Click to expand...
Click to collapse
You could do a raw disk image such as created by "dd" (and name it with an ISO extension even though it isn't), but I'd have to do more work to enable write access. All the work is done by the kernel which wants a raw disk image.
Sent from my ONEPLUS A3000 using Tapatalk
Can whatever it writes to the system be unwritten? Would I be able to take and OTA update after using this if I removed it and the ISO files?
stevenswall said:
Can whatever it writes to the system be unwritten? Would I be able to take and OTA update after using this if I removed it and the ISO files?
Click to expand...
Click to collapse
No! Full OTA only. Its not about the changes made. Your /system partition is on an ext4 filesystem which is journalled. Every write changes metadata and the journal. Incremental OTAs generally will change data block by block, and there is no telling what blocks it will change. The ISO files and APK aren't on the system partition and won't affect anything.
There is an older version of this that doesn't write to the system partition at all, but you have to set the ISO with the cable unplugged and then plug in your USB. The moment you change USB in any way, such as turning on MTP, the oneplus init scripts will revert the configuration back to the default USB drivers. Turning the USB drivers ISO into a symlink is what lets it survive MTP being turned on and is minimally invasive and revertable, but it still modfies blocks in the filesystem. If you want the older/safe one I can put up the link, just know that MTP and this can't be on at once with the old one since OnePlus has a bug that keeps turning off MTP (same thing that reverts the ISO).
I'm actually pretty sure it will be safe, but I personally wouldn't chance it and am recommending against it. The best bet would be to make a Magisk module, but I'm planning on replacing Magisk with something of my own, so I can't really spend time on such a solution. Since you've already rooted, using full OTAs over incremental is generally the method most people use anyway and will be totally safe. A system update will set your ISO back to USB drivers, just set your new ISO with the app again and it will be fine.
Sent from my ONEPLUS A3000 using Tapatalk
Thanks! Why not publish it as open source on github and put it on F-Droid?
Is it possible to have a windows 10 iso to boot in uefi mode with this tool?
installed the app but can't see it in app drawer can't open it!
my mistake.
i tested it and it works but without boot option. can u enable the option to write on the image? not read only?
and i tried to mount a windows installation iso and it doesnt work properly. i want to connect the phone to usb and boot from it to install
windows and other operating systems... and use disk tools etc
what can i\u do? thanks!!!
How can I use this on AOSPA Because you say it only works with the OnePlus File Manager. I got the apk for that but I cant install it because it conflicts with the current file explorer from AOSPA built in, I cant remove it with System App Uninstaller. Any solutions?
lindahl85 said:
Is it possible to have a windows 10 iso to boot in uefi mode with this tool?
Click to expand...
Click to collapse
Yes
DJArielLB said:
my mistake.
i tested it and it works but without boot option. can u enable the option to write on the image? not read only?
and i tried to mount a windows installation iso and it doesnt work properly. i want to connect the phone to usb and boot from it to install
windows and other operating systems... and use disk tools etc
what can i\u do? thanks!!!
Click to expand...
Click to collapse
An ISO is read only. It can't be written to. I have mounted a Windows install ISO just fine. What was the error?
R3dRacer said:
How can I use this on AOSPA Because you say it only works with the OnePlus File Manager. I got the apk for that but I cant install it because it conflicts with the current file explorer from AOSPA built in, I cant remove it with System App Uninstaller. Any solutions?
Click to expand...
Click to collapse
Actually, it only worked on OnePlus phones because it needed the USB setup used on OnePlus.
Somehow this thread got unmarked and I missed all the responded. Sorry! The good news is that I have a new Alpha version that should work on non-OnePlus devices and ROM's. This one doesn't touch the system partition either.
https://drive.google.com/file/d/1ZdSYIhs7pq8IrOZ4NBX4dzPSYP5tdeIh/view?usp=drivesdk
j03x2 said:
Thanks! Why not publish it as open source on github and put it on F-Droid?
Click to expand...
Click to collapse
Source is on my Github
Wait so how do I use this? I selected to open the ISO with the app, and I granted root, and it said iso location, etc.
I plugged it into my PC via USB but I'm not seeing a bootable option...
Edit now I see a usb item but it tells me grub incorrect filesystem or something
I'm trying an Ubuntu iso
NateDev said:
Wait so how do I use this? I selected to open the ISO with the app, and I granted root, and it said iso location, etc.
I plugged it into my PC via USB but I'm not seeing a bootable option...
Edit now I see a usb item but it tells me grub incorrect filesystem or something
I'm trying an Ubuntu iso
Click to expand...
Click to collapse
If you got to rub that it's actually booting off of the phone. It's up to the iso manufacturer to make sure that you can boot off a USB CD-ROM. So the phone is working, it's something in the iso that's messed up. Try a different ISO image
It doesn't seem to work on OOS beta 25 - app opens, reads something, tries to change usb mode (I can hear disconnect and connect sounds on Windows), returns to MTP and then closes itself.
Is this because of system being beta or custom kernel?
Code:
04-24 18:22:07.049 5923 9743 I ActivityManager: START u0 {act=android.intent.action.VIEW dat=content://pl.solidexplorer2.files/storage/emulated/0/Documents/ISO/ubuntu-18.04-beta2-desktop-amd64.iso typ=application/x-iso9660-image flg=0x10000001 cmp=systems.eddon.android.cdromswitcher/.MainActivity (has extras)} from uid 10091 pid 11517
04-24 18:22:07.065 560 560 E ANDR-PERF-MPCTL: hint lookup failed
04-24 18:22:07.067 5923 9743 E ANDR-PERF-JNI: com_qualcomm_qtiperformance_native_perf_io_prefetch_start
04-24 18:22:07.079 5923 9743 E ANDR-PERF-JNI: gIOPHAl initialized
04-24 18:22:07.079 5923 9743 E ANDR-PERF-JNI: gIOPHAl calling iopstart
04-24 18:22:07.079 559 559 E ANDR-IOP: IOP HAL: Received pkg_name = systems.eddon.android.cdromswitcher pid = -1
04-24 18:22:07.094 5923 6352 D RestartProcessManager: Duration is too short, ignore : 861 in pl.solidexplorer2
04-24 18:22:07.097 560 560 E ANDR-PERF-MPCTL: hint lookup failed
04-24 18:22:07.097 5923 6352 D RestartProcessManager: Update Total Launch Times :systems.eddon.android.cdromswitcher
04-24 18:22:07.097 5923 6352 D RestartProcessManager: updateSelf : systems.eddon.android.cdromswitcher, size : 13
04-24 18:22:07.098 5923 6352 D RestartProcessManager: Increase Total Launch Time : systems.eddon.android.cdromswitcher, times : 6, index : 12
04-24 18:22:07.098 5923 6352 D RestartProcessManager: Last Running Package : systems.eddon.android.cdromswitcher , start time 1524586927097
04-24 18:22:07.132 11826 12327 D TextDisplay: URL: /storage/emulated/0/Documents/ISO/ubuntu-18.04-beta2-desktop-amd64.iso
04-24 18:22:07.132 11826 12327 D TextDisplay: Using scheme content
04-24 18:22:07.133 11826 12327 D TextDisplay: Using filename: /storage/emulated/0/Documents/ISO/ubuntu-18.04-beta2-desktop-amd64.iso
04-24 18:22:07.133 11826 12327 I writeToSystem: Starting root commands
04-24 18:22:07.137 11826 12327 I suwait : Aquiring root!
04-24 18:22:07.162 468 12330 D Magisk : su: request from client: 22
04-24 18:22:07.162 468 12330 D Magisk : su: request from uid=[10176] (#1)
04-24 18:22:07.163 468 12330 D Magisk : su_db: query policy=[2]
04-24 18:22:07.164 468 12330 D Magisk : su: waiting child: [12331]
04-24 18:22:07.164 12331 12331 D Magisk : su: child process started
04-24 18:22:07.166 12331 12331 D Magisk : su: argc=[3]
04-24 18:22:07.166 12331 12331 D Magisk : su: argv[0]=[su]
04-24 18:22:07.166 12331 12331 D Magisk : su: argv[1]=[-]
04-24 18:22:07.166 12331 12331 D Magisk : su: argv[2]=[root]
04-24 18:22:07.166 12331 12331 D Magisk : su: pts_slave=[]
04-24 18:22:07.167 12331 12331 D Magisk : su: use namespace of pid=[12328]
04-24 18:22:07.186 11517 11535 D OpenGLRenderer: endAllActiveAnimators on 0xbb759b00 (SEGridView) with handle 0xd1a199a0
04-24 18:22:07.200 6682 6682 I GoogleInputMethod: onFinishInput() : Dummy InputConnection bound
04-24 18:22:07.200 6682 6682 I GoogleInputMethod: onStartInput() : Dummy InputConnection bound
04-24 18:22:07.204 5923 6361 I ActivityManager: Displayed systems.eddon.android.cdromswitcher/.MainActivity: +99ms
04-24 18:22:07.394 12332 12332 W ADebug : Failed to get property persist.sys.media.traces
04-24 18:22:07.405 12332 12332 D AndroidRuntime: >>>>>> START com.android.internal.os.RuntimeInit uid 0 <<<<<<
04-24 18:22:07.580 12189 12262 I NetworkController.MobileSignalController(2): showDisableIcon:false
04-24 18:22:07.798 5923 6541 I SettingsState: [PERSIST START]
04-24 18:22:07.850 5923 7879 I OpenGLRenderer: Initialized EGL, version 1.4
04-24 18:22:07.850 5923 7879 D OpenGLRenderer: Swap behavior 2
04-24 18:22:08.069 12332 12332 D AndroidRuntime: Calling main entry com.android.commands.am.Am
04-24 18:22:08.099 12332 12332 D AndroidRuntime: Shutting down VM
04-24 18:22:08.138 11826 12327 I suwait : I am root
04-24 18:22:08.138 11826 12327 D powrite-send: cat /sys/class/android_usb/android0/functions
04-24 18:22:08.158 5923 6524 D DebugKeepScreenOn: Acquiring screen wakelock due to Window{a0aa7c u0 Toast}
04-24 18:22:08.340 11826 12327 I powrite#: mtp,mass_storage,hid
04-24 18:22:08.340 11826 12327 D powrite-send: echo 0 >/sys/class/android_usb/android0/enable
04-24 18:22:08.441 7726 12141 E MtpServer: request read returned -1, errno: 5
04-24 18:22:09.077 560 625 E ANDR-PERF-OPTSHANDLER: perf_lock_rel: updated /sys/class/scsi_host/host0/../../../clkscale_enable with 1
04-24 18:22:09.077 560 625 E ANDR-PERF-OPTSHANDLER: return value 2
04-24 18:22:09.541 11826 12327 D powrite-send: echo '/storage/emulated/0/Documents/ISO/ubuntu-18.04-beta2-desktop-amd64.iso' >/sys/class/android_usb/android0/f_mass_storage/lun/file
04-24 18:22:09.743 11826 12327 D powrite-send: cat /sys/class/android_usb/android0/f_mass_storage/lun/file
04-24 18:22:09.945 11826 12327 D powrite-send: echo 1 >/sys/class/android_usb/android0/enable
04-24 18:22:10.123 5923 5923 W WindowManager: removeWindowToken: Attempted to remove non-existing token: [email protected]
04-24 18:22:10.146 6665 6665 D HeadsetPhoneState: Enter onSignalStrengthsChanged
04-24 18:22:10.146 11826 12327 I writeToSystem: All DONE! SUCCESS!
04-24 18:22:10.146 6665 6665 D HeadsetPhoneState: Exit onSignalStrengthsChanged
04-24 18:22:10.150 5923 6549 V UsbDeviceManager: USB UEVENT: {SUBSYSTEM=android_usb, SEQNUM=22690, ACTION=change, USB_STATE=DISCONNECTED, DEVPATH=/devices/virtual/android_usb/android0}
04-24 18:22:10.151 12189 12262 I NetworkController.MobileSignalController(1): showDisableIcon:false
04-24 18:22:10.238 5923 6549 V UsbDeviceManager: USB UEVENT: {SUBSYSTEM=android_usb, SEQNUM=22691, ACTION=change, USB_STATE=CONNECTED, DEVPATH=/devices/virtual/android_usb/android0}
04-24 18:22:10.240 5923 6359 D UsbDeviceManager: broadcasting Intent { act=android.hardware.usb.action.USB_STATE flg=0x31000000 (has extras) } extras: Bundle[{host_connected=false, connected=true, unlocked=false, config_changed=false, mtp=true, configured=false}]
04-24 18:22:10.263 7726 7726 W libc : Unable to set property "sys.usb.ffs.mtp.ready" to "1": error code: 0x18
04-24 18:22:10.264 5923 9743 I UsbDeviceManager: isUsbDataUnlocked: 0
04-24 18:22:10.310 5923 6549 V UsbDeviceManager: USB UEVENT: {SUBSYSTEM=android_usb, SEQNUM=22692, ACTION=change, USB_STATE=CONFIGURED, DEVPATH=/devices/virtual/android_usb/android0}
04-24 18:22:10.311 5923 6359 D UsbDeviceManager: broadcasting Intent { act=android.hardware.usb.action.USB_STATE flg=0x31000000 (has extras) } extras: Bundle[{host_connected=false, connected=true, unlocked=false, config_changed=false, mtp=true, configured=true}]
04-24 18:22:10.338 7726 7726 D MtpService: starting MTP server in MTP mode
04-24 18:22:10.534 5923 6524 D DebugKeepScreenOn: Releasing screen wakelock, obscured by Window{e3dd695 u0 systems.eddon.android.cdromswitcher/systems.eddon.android.cdromswitcher.MainActivity}
04-24 18:22:10.581 14627 14735 I PlayCommon: [373] com.google.android.play.b.h.e(263): Preparing logs for uploading
04-24 18:22:10.582 14627 14735 I PlayCommon: [373] com.google.android.play.b.h.e(267): No file ready to send
04-24 18:22:12.194 5923 6352 D RestartProcessManager: increase duration : 5090 for systems.eddon.android.cdromswitcher
04-24 18:22:12.196 560 560 E ANDR-PERF-MPCTL: hint lookup failed
04-24 18:22:12.196 5923 6352 D RestartProcessManager: Update Total Launch Times :pl.solidexplorer2
04-24 18:22:12.196 5923 6352 D RestartProcessManager: updateSelf : pl.solidexplorer2, size : 13
04-24 18:22:12.196 5923 6352 D RestartProcessManager: Increase Total Launch Time : pl.solidexplorer2, times : 14, index : 12
04-24 18:22:12.196 5923 6352 D RestartProcessManager: Last Running Package : pl.solidexplorer2 , start time 1524586932196