Hello, all ROM makers, developers, hackers and advanced users.
I have a problem and hope you can give me some good advice.
Here is my sad story
You can read the full description if you want. Or you can skip it - the main question in the end of this post..
I have bought a new Sony ericsson Live! with walkman (wt19i) phone during my newyear holydays in Prague. It seemd to be working fine.
It is from rev.3, manufacture date 11/49 (mounth/week)
When I came back home and started using it, I saw that after some inactivity period (about couple hours or maybe more) the touch screen, back and menu snsor buttons stops any responsing. Hardware buttons (home, volume, camera, walkman and power) are still working. The system also continues to work as usual, so I can turn it on (but can not slide to unlock), I can hear if somebody calls me (but can not answer). Alarms, notifications and all another functions are still working.
Once or twise it started to work again (by itself, without any actions by me) but after few time the problem repeated. I was very unhappy and sure it was a hardware problem (and of course the Czech warranty does not work in Russia), but now i'm not so sure.
The phone had 4.0.2.A.0.58 firmware (android 2.3.4) from the box. First of all I tried to install SE PC Companion software, connect phone with usb and make factory reset... touchscreen started to work! But soon I saw this problem again.
The next day a new update was released and installed it (firmware .62). My phone was working again, but with the same result after some time.
You shoud know, that simple softreset (or ejecting and inserting battery) has absolutesy no effect on problem. After system starts I can not even unlock it. But flashing a new (or even the same) firmware (with flash tool or SE PCC) makes touchscreen and buttons working for some time. Have no idea why, but installing ROM with CWM (even with full wipe) does not make touch working.
Then I tried to use another custom kernels and ROMs. I unlocked the bootloader with fastboot tool, flashed one of custom ROMs from this forum (pre-rooted and with CWM). Then tried to use CM7.2 ROM... then another kernel and another ROM. Official, official-based, totally unofficial. The problem was with me each time after couple hours
I thought it is because some troubles in lock screen. Tried to install "no lock" app, so my phone did not use lock... but after some time touch freezes in home screen.
I disabled screen off while charging in settings and tried to leave the phone "wired" for some time... actually it worked fine all the time, and when I dicsonnected it it was still working... for couple hours.
I tried to install "no sleep" applications that does not allow CPU and screen to suspend. But it have no influense.
I even flashed CM9.0 ICS (very) beta ROM with the same result.
If it is just hardware problem - why it solves (for some time, but solves) with flashing? If it is a software problem - why it doesnt solve with new kernels and ROMs? My brain is ready to explode.
Now I have only one last idea and ask you to help me.
The question is:
How can I use adb or adb shell comands to get more information about the problem with touch?
I saw there is some log (logcat, stderr) tools, debug tools. I saw working lsmod, dmesg and mount commands in shell.
I think I shoud get all this information when all is ok. And then get it again when touch stops working and then compare, is it a good idea?
Where exactly shoud I see? How to test or get some touch input device info with adb? Is there any item in /dev that i can explore? Or something in dmesg? Where are touch driver located and how can I check if it is working?
I have some basic linux and andriond skills, but have not enought expierence.
I very (VERY) hope somebody can give me any useful advice to continue solving the problem. Where to see, what to do?
Thank you
P.S.: and sorry for mistakes, of course. English is not my native language.
P.P.S.: i am not sure where is the best place for this question: here or in xperia subforums. But I decided that this question is not xperia-specific and can be useful for other people in future.
Anybody? I have Lenovo Yoga B6000 with touchscreen problem and will be good if anyone know how can i test TS through ADB or shell.
Related
First of all I would like to apologize for not so perfect English
I have U8650 and i would like to make this topic general topic for it. I know there are few topics but there is no much info in them.
I have made same topic on croatian forum for phones so i think it will be better if its on xda because there are much more people that are good in cooking cracking etc.
So lets begin
Detailed specifications can be seen on the LINK, however, the battery is 1400mAh[/ B] and not 1250 (i have sent email to gsmarena to change it but nothing hapend...)
ROOT and the original ROM
After playing with the phone I wanted too root it, after a good deal of trouble, and around 40 readed topics (without overdoing it) I came up with some knowledge, of course the problem is that the phone is currently on only few markets. (spain, croatia, turkey, australia and china i think)
To root U8650 you should flash it with original Rom, Spanish devices dont need original rom to root dont know why it is but it is
ROM
It is necessary to download an official ROM
LINK
After you download it unrar it and dload folder copy to memory card
Path should look like \ dload \ update
to flash device you need to
turn it off
remove the battery for 5 seconds
put the battery back in
press the buttons "VOL +" + "VOL-" + "ON" (all three keys at once)
and will start automatic firmware upgrade
for 3-4 minutes cell is debranded
If you get error not found firmware that means that you did not put the firmware on the SD card like you should (I got it a few times) just off the device and repeat the procedure.
root
After flashing unbranded firmware we can throw at root
software needed for the root LINK
This is similar to debranding.
download root file
Put it on SD card
turn off the phone
remove the battery for 3 seconds
Press "VOL +" + "ON" (without the vol-)
When you open the "bios like" menu use the volume keys up/down to select the update from memory card called root
after this procedure just reboot the phone and you have rooted phone
UNLOCK
My wife is on vip network so I had need to unlock cell
Recommendation for Tibor Szabo's
[email protected] [/ email]
contact the man, he tells you to pay € 13 at [email] [email protected] [/ email]
Send him mail with the payment for approximately 12 hours with you (he said 2-3 days al always come to 24h)[/SIZE]
if this is forbiden on xda i will remove it
If you have any questions please ask, this all is wrote on xda and some other forums i just put all together
[B]Do not think i am responsible if anything goes wrong I have done in exactly those steps and everything works normally. Everything you do yo do at your own risk.[/B]
So: D after a slightly longer introduction with u8650 came the day to put Custom rom.
Of course, for custom rom you will need root thus described above tutorial.
After puting custom rom phone is like 20% faster
few main features
Integrated flash (load all ads from the flash) loads test flash from Adobe i didnt test it much more because yesterday i put custom firmware
new driver for the camera from turkcell that means 5MP camera resolution
Better battery life
overclock processors at 780MHz (you can set it manualy)
Here is the complete list of modifications that is taken with [URL="http://www.htcmania.com/showthread.php?t=262489"]LINK[/URL]
In principle, this entire tutorial is taken from [B]Zadkyn[/B] and translated becuse he is hard spanish guy nothing is on english he is not very good at answering questions but thanks to him we have custom roms and all the improvements.
list of improvements (in English)
[QUOTE]Overall performance improved a lot (it is also the little battery somprendente Spends now even with the 3G)
-Changed icons graphically and manufactures factory setting, added percentage battery icon factory
-Added adobe flash compatible and running (with the strip overlock well)
-Lower spending on drums (set the minimum cpu for this)
-Restored and changed some other applications (all zipiling passed by lower consumption of RAM)
-GPU rendering enabled
Battery-drain slower, less consumption.
Grate black-on camera to make photo with overlock fixed
Overlock-stable up to 780 (no more restarts) to give to more than 722 problems.
-Added and removed other applications
Overlock-Kernel to 844
Unlocked-Kernel
-Operates any headphones
New menu-configuration, more optimized and icons removed rom China.
Bootanimation custom-added, now you can put your wish bootanimation
-Added run-part BusyBox
-Added Apps2SD
Added bash-shell
Zipalign all-in app
New-look graphic
Huawei-optimized new launcher (and consumed as Zeami or less)
-Fix bootanimation
Init.d-scripts folder added
Scrip-added ramscrip
-Applications optimized to consume less RAM
Boot-unlocked
-Data Applications (to uninstall and market updates)
Root-shell
-Added new root
Application-Acrchivos disassembler (ODEX files only is crap and problems)
Removed sea processes on startup
-Original Sources
-Some of deleted applications including Telstra
-Optimize graphics
New Market-added
New menu-bright
-Back to the white menu
-Implement improvements in order to run 3D accelerated 3D notification bar
Added applications-highly recommended.
-More RAM optimized for removing (less processes on startup)
Optimized sub-mic, and works well, you can check any call recording.
Completely changed-Topic icons like systems.
-Removed garbage Telstra [/ color]
, As implemented VoIP, voice dial ip menu to call.
Configuraccion-optimized menu and changed the color to black.
To-quality photos and video recording improved.
Jpg Image-Viewer improved.
-Pixel camera increased significantly (software, which the Turks have for any)
Best answer-ram and optimization (42m).
-Red 2 g 3g and improved (more coverage)
Energia-saving implemented.
Netfilter-range increased.
Less force-closure errors in some applications as well as more support.
-Some more things.[/QUOTE]
I put 1.5 version because it has corrected a couple of bugs.
Biggest object is that he removed default camera app imho it's not a problem because you can instal lg camera.
So here is tutorial
What you will not learn from linked topic (and I found out by sheer luck) is that you need to install drivers and custom "bios" to be able to put custom rom
So first things first
You will need to do procedure in this topic [URL="http://www.htcmania.com/showthread.php?t=256095"]LINK[/URL]
First download the driver for Windows 7 [URL="http://www.mediafire.com/?3bvp3p42t4iqwt2"]LINK[/URL]
So these are the drivers that you install and run you will have a screen with two options press instal drivers
If you have XP and these drivers dont work download this [URL="http://www.mediafire.com/?20qkr711ceuna0n"]LINK[/URL]
I have W7 so I leave to you if this is working for xp (it should work because no one has yet complained )
The second step is to download this file [URL="http://www.mediafire.com/?k421vgl3xy1fgpa"]LINK[/URL] unzip it and run Instalador.bat
You have fine hacker green screen and bunch of Spanish. luckily it doesn't interest us. Go to the next step and that is putting the phone in Fastboot mode.
The third step unplug the battery cell out/in pressing VOLUME - (or the volume down) and the power button and hold for 10 seconds.
it will show you only the Huawei logo and it should only show you that.
Step Four Connect the mobile phone with the USB cable, wait until computer detects it and after a few seconds go ti fine spanish green screen and press any key
It will flash "bios" of the phone it should be ready in a minute or two there is no hurry.
then reset the cell and you should have a fine new "bios".
Check this by turning off cell battery out / in and press the Volume + (volume up) and the power button for 10 seconds.
It should appear with orange letters like from the picture
[IMG]http://postimage.org/image/2d31ltan8/[/IMG]
After you have fine new "bios" you want to put fine new rom
The first step with this rom download [URL="http://www.mediafire.com/?8qd05qhv5flhips"]LINK[/URL]
The second step is to put the zip in the root of your memory card.
The third step going into the BIOS mod So turn off the cell battery out / in the volume + power button for 10 seconds.
You get orange letter menu now navigate with the volume + and - and with the power Buton you confirm it.
The fourth step choose the factory data wipe, then wipe the cache and then advanced wipe devil cache (not the exact name but you will seen it)
Each time when you choose wipe you need to confirm it, always navigate to yes i want to wipe.
Fifth step Return to start of the BIOS and select the custom recovery and navigate to the zip file called zadkin and select it.
When you choose it will start to flash for me lasted about 4minute when it's finished, reboot the system and if everything went well (and there is no reason why not) you will get the boot menu with zad logo.
For first time cell loaded few minutes so patience.
After that you have a nice Costum rom that is faster and more economical with better battery life stronger processor and better camera
If you have questions feel free to shoot.
The same as in the first part of post you do all on yours risk and I am not responsible for any problems and errors. I did everything according to these instructions and I got what i wanted.
[B]CODES[/B]
codes for the service menu
[B]*#*# 2846579 #*#*[/B]
code for the info on your phone
[B]*#*# 4636 #*#*[/B]
All of this is wroted on few forums and i just wanted to put all in one place on the most visited forum for android (xda)
Also i would very like if someone with more expirience can read this tutorial and suggest something.
one more thing that i left out is RAM limitation and i hope to get some answers about that.
also if this helps someone feel free to thank me
Best regards
just flashed your custom rom without problems. its amazing what people can do..!! it seems based on the yoigo firmware and you have english and spanish as languages. everything you need is included filemanager app2sd etc. i like it very much.. thanks.
edit: could you kindly tell what the flashing of the bios (with pc) exactly is for?! thanks
If you dont flash that bios you cant wiPe devilk cache and you cant instal modified rom so basicly puting new bio is must for moded roms
It will be great if someone else can try this
As for wiping the data, there was only one thing possible to wipe. everything else was just a line of "NO" without option to change it.
I now have like 3 programs running in background thats cool... and of course its cool that many programs are removed that cant be removed otherwise (like documents2go trial)
But thE stock yoigo firmware is good too... It already comes with the possibility to install apps to SD u dont need extra program for that
EDIT :and i just come back to phone.. i left it on charger over night.. and its in the orange BIOS MODE !!!! so it crashed i guess ??? bad
EDIT2: Couldnt access 3g internet even tho i had the right profile .... will test some more
Unofrtunately the custom ROM has still a lot of bugs, be careful :-(
yeah its BS... i am going back to original yoigo at least there i can make it install all aps to SD automatically .... this hacked firmware cant even transfer most new aps to SD..
i hope i will have no problems cos of flashed bios...
thanks anyways both of you
edit: 2 more bugs.. adblock dont work (some java error crash) and the 11mb adobe flash cant be copied to sd or removed at all
out of 27 apps (a few downloaded by me) 7 can be copied to SD and 20 cant
is there anyone who tested cyan mode for this phone ?
this guy
http://translate.google.de/translat...ania.com/showthread.php?p=2880783#post2880783
check that forum out they also have Cyanogen7.2-benru89 [Android 2.3.7] [LEDs] !!
do anybody knows how to make back key to just leave app and not go to home screen
i have instaled cyan 7.2 spartan 1.2 ver and when i enter app drawer and start app lasts say camera i push back key and it lands me in home screen and not in appdrawer.
hope you understand what i am saying
problem
I had a problem when i tried to root my phone. I copyed the zip file into my sdcard but it could find the file.
I got other things in my sd if it matters idont know.
I would be very thankfull if someone could help me!
huawei u 8650 phone is dead
hi ,after installing official firmware ,my phone got brick.i also made backup with cwm recovery,but now my phone only show black screen only alittle blink of light when i push power bottom,how can i solve this problem
I don't understand, if you root your phone yo unlock it from its carrier? I mean, free to use with whatever sim card from any mobile company?
Didnot work on U8652
12/14/11: I tried the rom upgrade on U8652 ATT fusion and received "install error' after unpacking.
Any suggestions?
12/15/11: I successfully installed the 'recoveryclockmod' after finding the proper android usb driver for winXp - 'pulse drivers'
then installed the custom rom. But the phone details on the installed custom rom says its a U8650 model not U8652.
Thanks OP
Thanks OP
I followed your instructions and installed recoveryclockmod and cyanogen_u8650-benru on my U8652. Now I finally have root and a nice ROM to play around with. Thanks OP
Does the root part work on a Huawei U8650 Sonic that came with android 2.3.5 and newer ROM ( U8650V100R001C343B851 ) ?
I need to root it to be able to use reverse USB tethering
dark0153 said:
Does the root part work on a Huawei U8650 Sonic that came with android 2.3.5 and newer ROM ( U8650V100R001C343B851 ) ?
I need to root it to be able to use reverse USB tethering
Click to expand...
Click to collapse
Try with
http://unlockroot.com/
From lastest version they support huawei U8650. You can always put recovery and custom rom (google htcmania or read first post)
sipe1 said:
Try with
unlockroot.com
From lastest version they support huawei U8650. You can always put recovery and custom rom (google htcmania or read first post)
Click to expand...
Click to collapse
unlockroot doesn't work, i tried the latest version (2.2) and i get the same error "Failed to get shell root !"
I have fried my U8650
I attempted a firmware update (official)... stage one completed... phone restarted and got stuck with a grey screen (no logo nothing just blank grey screen) all the soft buttons are turned on. constantly.
It wont go in to recovery, a simple touch to the power button turns it on and then it wont turn off unless I take the battery out.
I tried flashing with DC unlocker but my system wont detect it, I have installed the drivers provided at huawei site.
the phone was just a week old and am real pissed.
worst part, i did all that after reading this post
Anyone has any idea, how i can get it to work once again.
friedroid said:
I attempted a firmware update (official)... stage one completed... phone restarted and got stuck with a grey screen (no logo nothing just blank grey screen) all the soft buttons are turned on. constantly.
It wont go in to recovery, a simple touch to the power button turns it on and then it wont turn off unless I take the battery out.
I tried flashing with DC unlocker but my system wont detect it, I have installed the drivers provided at huawei site.
the phone was just a week old and am real pissed.
worst part, i did all that after reading this post
Anyone has any idea, how i can get it to work once again.
Click to expand...
Click to collapse
I didn't try this method and I'm only suggesting it because it sound like you almost bricked your phone.
You could try installing ClockworkMod recovery using fastboot (here is a guide for that androidforums.com/sonic-all-things-root/476263-root-guide.html just follow 1-9 ) and then flash the original rom for your phone (I found a list of stock roms here android.modaco.com/topic/350367-huawei-u8650 )
Dont forget to wipe data/cache before flashing the new rom ( this might be the cause for the state your phone is in now )
Update:
Got the drivers by installing hi space and letting it search for appropriate drivers. Worked real smooth.
Now Computer detects phone. But the instalador.bat keeps on searching for device :S
Stuck and stumped once again.
I want to believe but all I see is darkness... or a mildly lit lcd with greyness to be precise. thoughts, ideas anyone.
Thanks man. A ray of hope finally.
Only one problem.
My system won't detect the phone. When i plug it in via usb, it turns on. I mean all the buttons turn on, screen turns dark grey from dead black. But that is it. Computer wont detect it. I am running on windows 7.
Another system detected it which was running on XP but it wouldn't accept the drivers.
Dear Experts,
Months ago my 2y old XZU on 4.4.4 (6833, towel rooted, locked, CWM recovery) started to fail on init of LCD, when coming out of standby. LCD init not only fails when device gets waked up by "power" button, but also when power is applied (Dock connector or USB). So I guess in fact it is a firmware issue (not a defective power button or the like).
It gets worse and worse; when device is warm it sometimes needs 30 or more off/on cycles.
When LCD init fails, the screen either stays black (only backlight) or colored lines show up shortly and fade away. But in fact the device is running - only LCD is not working.
But when init is successful, the XZU can run nicely for hours (as navi).
I hope that a android FW update might help!?
Unfortunately OTA doesn't seem to work on routed devices even with still locked boot loader.
Is there a way to update directly to 5.1.1 available now? Is it possible to update in two steps?
I would not mind to loose root, but loosing the possibility to write to external SDCARD!
Any help/ideas? THANKS A LOT!
Thomas
Sounds like SOD, or Sleep Of Death. The Ultra had some issues with it back on Jelly Bean, but I hardly read about it being an issue on KitKat, but yeah, it's probably a software issue, so an update to 5.1.1 might just cure it. You have a couple of options here:
1. Update the official way by installing Sony's PC Companion app on your computer and updating it that way
2. Update it in a little less official way by updating it manually yourself with Flashtool on your computer
3. Update by flashing a customized version through a recovery system on your device (like CWM or TWRP)
I would personally update it through PC Companion if I were you, since I guess you're not that technical when it comes to flashing and troubleshooting things. PC Companion should notify you about the update as soon as you plug your Ultra to your computer. If it notifies you about the 5.0.2 update, then I guess you'll have to update to 5.0.2 first, and then you'll be able to update to 5.1.
Flashtool allows you to manually download a FTF, or the ROM file from XDA and then flash it yourself. It's a lot quicker than PC Companion, but also a lot more complicated for people who haven't used it before.
Flashing through a recovery is mainly for people who already are used to flashing and stuff like that, and know what they're (mostly) doing.
Any other questions?
Thanks for your very valuable hints!!!
I'm really curious if it will work with PC comp (vs. OTA) and if I will loose write access to SDRAM (introduced in Android 4.4 and regained by root and SDFix).
Currently the download is running..
Will post results
zamzon said:
Thanks for your very valuable hints!!!
I'm really curious if it will work with PC comp (vs. OTA) and if I will loose write access to SDRAM (introduced in Android 4.4 and regained by root and SDFix).
Currently the download is running..
Will post results
Click to expand...
Click to collapse
The OTA will only tell you to connect to the computer to update. And regarding SD-card, that won't be an issue. Android will ask you to grant permission to the SD-card in some cases, but I haven't had any issues with it. Most if not all file explorers works just fine, and you won't experience any issues with the SD-card.
The update worked (no error on PC), but device seemed dead afterwads
After a reset and numerous power off/on cycles, the LCD init worked and I could see the result. :laugh:
Root was gone, of course. Recovery system and write access to SDCARD, too. Therefore Sygic app (navi), which had been moved to ext. SDCard. could not run anymore and moved itself to .android again.
But worst of all: the init of LCD now works even more seldom!
It does not even work when device has been shut down before, cooled down and is then switched on.
As far as I read, the SOD is different, cause my device in fact is "awake". It runs fine - only LCD is not working and not displaying anything.
I have no idea how to fix this. I can not imagine any hardware defect, causing such behavior (and I designed embeded systems with gfx controllers, myself).
Thomas
zamzon said:
The update worked (no error on PC), but device seemed dead afterwads
After a reset and numerous power off/on cycles, the LCD init worked and I could see the result. :laugh:
Root was gone, of course. Recovery system and write access to SDCARD, too. Therefore Sygic app (navi), which had been moved to ext. SDCard. could not run anymore and moved itself to .android again.
But worst of all: the init of LCD now works even more seldom!
It does not even work when device has been shut down before, cooled down and is then switched on.
As far as I read, the SOD is different, cause my device in fact is "awake". It runs fine - only LCD is not working and not displaying anything.
I have no idea how to fix this. I can not imagine any hardware defect, causing such behavior (and I designed embeded systems with gfx controllers, myself).
Thomas
Click to expand...
Click to collapse
But that does sound like a hardware issue. The final thing you can do, before you'll have to send it in for repairs, or get a new device, is to do a full factory resetting and see if that finally helps. You just updated now, but there's still a lot of crap left over from the previous version, that might screw things up.
So my advice would be to do a wipe, check if it help, and if not either send it in for repairs or get a new device. It's not a software issue if the issue travels over several OS versions with you. It may be a faulty display connector.
So I bought a new Poco F1 few days ago. And since I've been using it, I've been facing bugs.
So when I got the device it had Miui 9.6.14 installed on it. And I just wanted to unlock it and root it asap. As you know you have to wait 3 days to unlock it. But as soon as I put in the unlock request i.e by going to fastboot and on mi unlock it shows 99% complete then it says you have to wait for this much time.
As soon as I did that, I faced the first bug. That was related mobile network settings/usb tethering/*#*#4636#*#* code (engineering mode IDK). So when I clicked on usb tethering, turned off mobile data/wifi, or the phone lost signal, it rebooted, from boot splash (not boot logo). Maybe this was the ROM's way of preventing any big bugs why do I think that? I'll explain later. So after rebooting I could turn on/off usb tethering but not mobile data or wifi. I can turn them off as soon as the phone boots but if I do it later i.e. after unlocking the phone, it rebooted.
So this is one of the bugs that has been consistent, the one that never got away. Well sometimes it did went away but not for long. Like sometimes if I haven't turned off the internet in a long time or restarted the phone properly, the data turning on/off doesn't reboots the device, IF the device isn't connected in usb tethering. Like few days ago I discovered that usb debugging could fixed it, but that didn't lasted long either. Sometimes turning off usb tethering then mobile data very quickly afterwards worked, but didn't lasted long or only sometimes it would work.
So the advice I got earlier was that, just flash a new software. While I didn't technically flashed the new software, I flashed the similar software, deleting all user data & everything, but that didn't helped. As it seemed in the beginning, that bugs weren't there but they started appearing later on. Now IDK if I used a locked un-rooted device, these bugs wouldn't appear, not too sure about that.
And you maybe saying, well you didn't flashed the newer version of the rom, then that's the problem, Well IMO it isn't. Here's why - So when I flashed the same rom, the phone got locked cause I forgot to select the "clean all" option in MI flash instead of "clean all and lock". So I unlocked it again, flashed twrp and as you may know that when booting twrp for the first time it asks you two options, "allow system modifications" & "read only". And the last time I flashed it I chose the read only option. But this time it didn't asked me. Now do you understand? As I'm not an expert in this, the guy who gave me this solution said maybe the device tree wasn't cleared. So how does flashing a new version is gonna make a difference if all of the files don't get deleted? If it's not gonna start fresh? I also used the command "fastboot erase recovery" (as suggested by that fella), that didn't helped either, just an FYI.
So I decided to install other roms, thinking maybe that could help. It seemed like working in the beginning but soon it started to fall down. First OS I installed, Pixel Experience, didn't had such bugs earlier, but there was a little one. If I disconnected the phone while it was in usb tethering mode, it would reboot the same way it did with miui. If you turned usb-teth off first, it didn't rebooted. So I thought I could live with that. But later more bugs started to appear. The same thing, turn off the internet and the phone restarts.
Remember when I first said maybe it was OS's way of not having bigger bugs, So that happened this time. New bugs like when I try to get into an app's info, the settings would crash (stopped working). BTW you could getting into an app's info if you are able to find the said app, by going into storage, then to apps. Moreover sometimes when I'd try to open the camera it would just show blank, or very dark image of the environment, not moving though, and sometimes, it would just work.
Then I installed Lineage OS. Didn't find such bugs, but I'm pretty sure if I do all this usb tethering stuff in there as well, I'm gonna find these bugs.
Now you might be thinking that how am I installing all these roms, well that's cause of MultiROM. And if anyone here is gonna say well that's the problem. STOP! Stop right there. These bugs were present there before I even used MultiROM.
Some other bugs I'm facing RN in Miui -
Auto Rotate not working. If I want to go landscape, I'd have to open an app/game that opens in landscape and switch from there, cause it gets stuck, vice versa for portrait. And you can only view it in default position i.e. you can't rotate to other landscape position if you wanted.
Camera not working, showing "can't connect to camera" error.
When I play offline games while these bugs occur. When I connect the headphones, the audio also comes out of the speakers. After I restart the phone properly, that stops. (This bug was also present in earlier stages when MultiROM wasn't used)
When going into second space, I created a txt file in mixplorer and when I try to open it, the system reboots. And I just checked by installing a root checker in second space, it says not rooted, wow!
When going to default file manager and tapping on storage, it said "disconnected" and few seconds later saying something like "couldn't add error 10000". This used to happen before but not now, neither I use the default file manager anymore. Though if I'm too quick and unlock the phone, open a file manager or any app that uses storage, it would go blank. Don't know if the storage crashes or something else. But after a restart, it's fine.
One thing, after the phone restarts when these bugs happen, "Find My Device stopped working" or something similar always appear, I don't remember the exact message.
[*]There are somethings Gcam related but I don't think they're 100% bugs related. Cause I installed the latest version on Lineage OS and it works as far as I used it even features like Night Sight and Slo Motion. Now those errors could be related to older android versions or something else IDK. Things like camera lagging in picture mode not in video mode and some version just straight up not working even when they're supported by older android 8.1.
Now could it be a hardware problem, IDK as I said I'm not an expert. These other bugs could've appeared cause of MultiROM or me flashing a new firmware over older rom version in order to install PE, again IDK.
Fair warning : If you're just gonna come here and say, Oh! this all cause of MultiROM or cause you didn't installed newer miui, then don't waste your time, cause I'm not gonna read any arrogant answers. Neither if you say, try to do this or that. I'm not here for that either. Cause if I wanted to do hit and trial, I could've done it myself
But if you understand the situation and can provide expert help, then only please reply. So if you're willing to help & understand properly, and you want anything from me, like logs etc. just tell me how to do it, I'll provide. Or if you know some way to do proper fresh install, only if that can fix the bugs so that I don't have to deal with them anymore, I'm looking forward to your reply.
I have a Galaxy S III GT-I9300 I bought in 2014. After three years, I downloaded a custom ROM from xda-developers (android 4.3 is all I remember about it) and installed it successfully. It worked alright until one day when I wanted to sell the phone and a customer wanted to buy it on short notice, and I rushed to delete my files from the phone, but I destroyed the Android... I connected it to my laptop and shift-deleted some system files.... since then, the phone is delaying when trying to unlock (if i lock it now and try to unlock it a few times, it opens harder and harder), when I'm using apps it continously shows that some .com processess stopped working, and if I try to turn on the bluetooth, the phone instantly freezes and restarts itself.
I tried reinstalling two original ROMs, (version 4.1.2) successfully, but the data on the phone&the system problems remain the same.
I'd like to know how can I make a hard reset, meaning in deleting all the files&settings as it was brand new, just to clear everything, like clearing CMOS. I also think the recovery mode is damaged and I'd like to fix it somehow (if this is possible). The installation process I did for installing the custom ROM from XDA-devs was long and complicated, I had to do a lot of things... and I just want to get the phone fixed and restore to default (or even to fix bugs on this android version) its android, kernel & everything could be ,,reflashed''.
I'm willing to pay if someone helps me fix the problems and it really works. Thank you!
I have a Galaxy S III GT-I9300 I bought in 2014. After three years, I downloaded a custom ROM from xda-developers (android 4.3 is all I remember about it) and installed it successfully. It worked alright until one day when I wanted to sell the phone and a customer wanted to buy it on short notice, and I rushed to delete my files from the phone, but I destroyed the Android... I connected it to my laptop and shift-deleted some system files.... since then, the phone is delaying when trying to unlock (if i lock it now and try to unlock it a few times, it opens harder and harder), when I'm using apps it continously shows that some .com processess stopped working, and if I try to turn on the bluetooth, the phone instantly freezes and restarts itself.
I tried reinstalling two original ROMs, (version 4.1.2) successfully, but the data on the phone&the system problems remain the same.
I'd like to know how can I make a hard reset, meaning in deleting all the files&settings as it was brand new, just to clear everything, like clearing CMOS. I also think the recovery mode is damaged and I'd like to fix it somehow (if this is possible). The installation process I did for installing the custom ROM from XDA-devs was long and complicated, I had to do a lot of things... and I just want to get the phone fixed and restore to default (or even to fix bugs on this android version) its android, kernel & everything could be ,,reflashed''.
I'm willing to pay if someone helps me fix the problems and it really works. Thank you!