Related
Hi
I installed the last XAD Carbon Rom 4.4.4 [29.06.14] on a brand new Samsung Galaxy S 5 SM-G900F (French model). I installed XBMC 13.2 Gotham – beta 1 too. Unfortunately the apk is unusable because S 5 touch screen isn't responsive at all, like if it was frozen. I only can increase or decrease the volume.
Thx for your help.
Olivier
ikvat said:
Hi
I installed the last XAD Carbon Rom 4.4.4 [29.06.14] on a brand new Samsung Galaxy S 5 SM-G900F (French model). I installed XBMC 13.2 Gotham – beta 1 too. Unfortunately the apk is unusable because S 5 touch screen isn't responsive at all, like if it was frozen. I only can increase or decrease the volume
Click to expand...
Click to collapse
No idea, I don't use either package. Surely you'd find better support in the ROM support thread though?
Did you wipe the cache partition?
Did you wipe the data partition prior to installing the ROM?
Did you install Gaps?
Did you see if the problem occurs before you install XBMC?
Did you search the Carbon support thread to see if anyone else has similar issues?
.
fffft said:
No idea, I don't use either package. Surely you'd find better support in the ROM support thread though?
Did you wipe the cache partition?
Did you wipe the data partition prior to installing the ROM?
Did you install Gaps?
Did you see if the problem occurs before you install XBMC?
Did you search the Carbon support thread to see if anyone else has similar issues?
.
Click to expand...
Click to collapse
Hello fffft and thx for your help.
As a nob, i can't post on the appropriate forum yet, but yes, i wiped all i was able to wipe. I installed the appropriate gapps too. The problem is specific to xbmx and didn't occur before.
Edit : I reinstalled a Samsung stock rom and xbmc works like a charm. The problem is inherent to that carbon rom.
Q&A for [ROM] I9500 Galaxy S4 OzcanRom v5.3 Aroma XXUGNH4 KitKat 4.4.2 (10.10.2014)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Please fix the screen flicker, and the rest is all good. Thanks for a great rom.
---------- Post added at 04:30 PM ---------- Previous post was at 04:23 PM ----------
Please fix the screen flicker, and the rest is just great rom.
I9500 Galaxy S4 OzcanRom v5.3 Aroma XXUGNH4 KitKat 4.4.2
Hi
no doubt your rom is best ever rom i used but me facing 3 different problems please guide me with any solution tht how can i solve these prblems
1st is the text message problem that it is limited to 3 pages that is 480 characters total then its stop like this image
2nd is shealth problem which is not calculating correctly u can notice that after walking almost 5000+ steps its still showing less then 1km distance which is not correct bcoz i walked the same way same time same steps on my stock rom which is almost 4km but on custom rom from 4.1 til now 5.3 its not working fine like this image
3rd is smart alert which was good in s4 stock rom like i put over my mobile from surface then it turns light on of screen so that i didnt need to press home button or unlock button on my phone to turn on em too searched for this on net but didnt find good solution
can any on help me ?? and really sorry for bad english Image link: tinypic.com/a/391zt/4
Lost Network
Guys,
I upgraded the rom from 5.2 to 5.3 and did the full advance wipe, format data and installed it by however I lost my network and I no longer get 3g connection. How can I fix this?
Themes
Is there themes options in S5 touchwiz launcher
ubercool786 said:
Is there themes options in S5 touchwiz launcher
Click to expand...
Click to collapse
There are two:
1. Basic.
2. Natural.
BALLZier said:
Guys,
I upgraded the rom from 5.2 to 5.3 and did the full advance wipe, format data and installed it by however I lost my network and I no longer get 3g connection. How can I fix this?
Click to expand...
Click to collapse
i think two solution.
in one hand, maybe you lost yours APN settings. so, you have to look up the company (movistar, personal, at&t, whatever) settings in google.
In the other hand, try to change your modem according to your region. there are a lot of helpful post in this forum where you can learn how to change it.
See you!
Stock kernel
When i installed the stock kernel version of ozcanrom 5.3, I got problems with apps such as swiftkey (keeps on failing to install language pack) and whatsapp (cannot take pictures or view them), so i realised that every app that i installed did not write to the system drive (there were no folders on system drive that showed that these apps were installed) but when i installed the custom kernel, this problem did not exist, so is there anyone who can help?
Magungqu said:
When i installed the stock kernel version of ozcanrom 5.3, I got problems with apps such as swiftkey (keeps on failing to install language pack) and whatsapp (cannot take pictures or view them), so i realised that every app that i installed did not write to the system drive (there were no folders on system drive that showed that these apps were installed) but when i installed the custom kernel, this problem did not exist, so is there anyone who can help?
Click to expand...
Click to collapse
Did you...
a. Apply the patch of fouldermount. Try to download this apps from Google play.
b. Wipe cache and delvik?
C.if nothing of above work, try to reinstall the apps. (In my first time I did that)
good
good
please upload rom in google drive
not sure about installing this rom
My baseband version is i9500dxufnb2, will my phone brick? (Sorry for inconvinience because I had bricked my phone many times installing other s5 rom)
apps does not access ro internal sd
It is good but the screent will never off when charging and a big problem for me is apps does not have any access to internal SD, how should I fix it????
ozcan rom v5.3 - whatsapp sharing and download failed
plz help. i already install this rom and my whatsapp doesn't work, can't sharing and download any file from msg.
How is the battery on this ROM?
Hi Guys!
How to fix the failure cache entry programs Ozcan v5.3?
Sorry for my English!
SoundCloud App Not Working.
I've been using OzcanRom since v4.x.
The Soundcloud App does not work on this ROM since a long time.
If there is a fix for this kindly share.
Same error
I have same error here. Is there any solution?
Everytime the ROM gets an update, I need to flash it all over again?
Great Rom for gt-i9500
I`m Currently using it on my s4 i9500 I LOVE IT
i used the s5 for a while and i don`t see any difference
only thing wrong :- when i use ultra power saving mode the xposed module keeps telling me to restart the mobile but i keep ignoring it
and i didn`t know that could have been from the rom but Soundcloud app is not working for me neither
Q&A for [ROM][CM10][CM10.1][CM-10.2][CM-11.0][GT-S7710] Samsung X Cover 2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][CM10][CM10.1][CM-10.2][CM-11.0][GT-S7710] Samsung X Cover 2. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Kosh_swe said:
Cm10.2 is all BUT stable! ...
My hardkeys (back/menu/home) stopped working ONLY on flxo/Vanir firmwares, ive tried both cm10.2 (20140204_cm_10.2_skomer-ota-eng.flx, which is supposed to be "rock solid", i dont want nightlies since this phone is going to my gf so im after a stable firmware) but i've also tried latest nightly vanir 4.4 but that got the same bug in it!
...
Click to expand...
Click to collapse
@Kosh_swe, have you found a solution? I also failed to get the Vanir ROM to work and I'd consider the flox CM10.2 ROM. Your post suggest that my radio would be dead in flox, too.
---------- Post added at 12:35 PM ---------- Previous post was at 12:26 PM ----------
Matt64 said:
Hey guys,
I recently compiled flxo CM11.0 rom with STE OMX support (from TeamCanjica).
I've been testing it for a couple of weeks, for me everything seems ok (no reboots, camera working ...)
I didn't test bluetooth hand's free, but it's certainly still broken.
You can download this rom from my dropbox account :
xxx
I'm also trying to compile Ubuntu Touch for S7710, I'll let you know when the rom will be flashable.
Click to expand...
Click to collapse
@Matt64, could you provide a hands-on on how to do the compiling?
Never mind, fixed my radio issue. See http://forum.xda-developers.com/showpost.php?p=56293409&postcount=37
Testing radio issues
Hi to all,
I just tested radio issues on my phone. I was researching, why radio is not working.
Here are results, maybe it will help. Anyway, I have my GT-s7710 for testing and I can do some tests or catch some debug informations if needed.
It seems that problem why radio is not working is located in modem-supervisor process. In original firmware, this process is responsible for uploading firmware into dbx500 platform chip. But in CM, there is no such process.
I am not expert, but it seems to.
I tried to use old modem-supervisor process to make everything working.
Services line from original fw:
Code:
service modem-supervisor /system/bin/modem-supervisor -r -f /dev/dbx500_mloader_fw -i /sys/devices/platform/ab8500-i2c.0/chip_id -c monitor -t 0
but it needs to be changed because /sys/devices/platform/ab8500-i2c.0/chip_id changed to /sys/devices/platform/ab8505-i2c.0/chip_id
Problem is that firmware event for loading firmware is never generated and firmware is not uploaded.
I have some dumps and traces if you need them. Thank you for your work!
Lukas
loneraver said:
I tried it, and got none of the "known" issues. Give it a try. If you get any issues, you can always flash back to stock rom.
Click to expand...
Click to collapse
Your "tested" devices are just headphones, right?
The Problem is not the hearing part - the microphone signals are blocked...
if you have a real headset - please try with that one again and tell me
an idea
The 7580's phone hardware is almost identical to the 7710. The processor in the 7580-higher heights, but the hardware buttons and then there are all of the functions, but it has the 4.2.2 firmware, which allow moving to the SD card. Somehow it should possess to operate from 7710.
I'm Hungarian, sorry if the translation is wrong, happened with google.
Okay so I am having the same problem with HW buttons as many others before me...
http://forum.xda-developers.com/showpost.php?p=51234756&postcount=329
http://forum.xda-developers.com/showpost.php?p=51253847&postcount=333
http://forum.xda-developers.com/showpost.php?p=54973574&postcount=362
Click to expand...
Click to collapse
After clean 1st boot after the installation the buttons are working perfectly, but after reboot (2nd boot) they are not working properly. Only long presses are working (google search by long press of menu button, kill aplication by long press of back button, last apps by long press of home button).
So? There is no such responde on how to fix that..!
DaGrizzly said:
Your "tested" devices are just headphones, right?
The Problem is not the hearing part - the microphone signals are blocked...
Click to expand...
Click to collapse
In my cited post I refer to a previously made post where I listed the devices:
loneraver said:
I tested it with logitech ue9000 and samsung hs2000.
Click to expand...
Click to collapse
Both are real headsets with working mics.
Know it's OT but if it's true it's exiting:
Miui for our phone coming?
http://forum.xda-developers.com/showthread.php?p=58720490
Sent from my GT-S7710 using XDA Free mobile app
Sent from my GT-S7710 using XDA Free mobile app
Try other
this one is very very STABLE :
http://forum.xda-developers.com/showthread.php?t=2689010
XCover 2: BT hands free - Problem fixed yet?
Hey developers,
I was wandering if the BT problem has been fixed for Cyanogenmod Version 10.2 for XCover 2.
BT hands free. Connection/pairing works, but the audio path is broken.
Thanks a lot!
baseband wipe
I can't get Cyanogenmod 10.2 working. Everytime installation wipes my baseband.
When I install the Stock ROM SIM works again - but after flashing CM again also wipes baseband again.
My Installation-Tools:
Odin v3.07
CMW: 20140112_cwm-6.0.4.6_skomer_fixed.tar.md5
CM: 20140204_cm_10.2_skomer-ota-eng.flx.zip
Is there any chance to install the baseband (I think it's inside the modem.bin)?
No network available in Polish Play
I'm installing CM for my father in law on Samsung X Cover 2 and I'm facing problem with no available network.
I've tried CM 11 and CM 10.2 - both are running fast but both doesn't recognize any network operator.
CM11 has additional problem with hanging during shutdown.
I've found that Polish network Play has common problems with radio: like here
https://code.google.com/p/cyanogenmod4milestone/issues/detail?id=510.
But even I'm putting T-Mobile sim card then still phone doesn't recognize (phone is coming from Play but it is unlocked).
When I restored Play stock ROM then it works.
Could anybody help in this?
I cannot point link to logcat because new user limitation - pastebin URL part is rWttd9PH
sk_8x said:
I'm installing CM for my father in law on Samsung X Cover 2 and I'm facing problem with no available network.
I've tried CM 11 and CM 10.2 - both are running fast but both doesn't recognize any network operator.
CM11 has additional problem with hanging during shutdown.
I've found that Polish network Play has common problems with radio: like here
https://code.google.com/p/cyanogenmod4milestone/issues/detail?id=510.
But even I'm putting T-Mobile sim card then still phone doesn't recognize (phone is coming from Play but it is unlocked).
When I restored Play stock ROM then it works.
Could anybody help in this?
I cannot point link to logcat because new user limitation - pastebin URL part is rWttd9PH
Click to expand...
Click to collapse
Forget CM en try Vanir or MIUI these are more up2date. Also CM11 is alpa with camera bug:
First look at: http://forum.xda-developers.com/t/xcover-2
Vanir
Second, I use Vanir 4.4.4 daily. It has some bugs, but not some bugs that makes it unstable. Known issues:
Start/Stop navbar after every restart
Use this solution to fix connection errors after a fresh Flash: http://forum.xda-developers.com/showpost.php?p=60411469&postcount=612
Other small bugs:
2G/3G quick setting and normal settings dont work properly because of absence of LTE
Navigation Ring and immersive mode causes dead touch screen space
DSP manager doesn't work
After using Vanir 4.4.4 I never want to go back! It's that much faster, more free RAM en better battery performance. Because of the better RAM performance, you must kill apps more often else it will drain the battery quicker :silly:.
Best way to Flash with 4.4.4 is to first flash Clockworkmod through ODIN, then do the usual Full Wipe --> Wipe Cache --> Flash Rom --> Flash GAPPS. Here is a video of someone doing these things. P.S. in this video the process is speeded up also reboot can freeze the system (just remove battery after a couple of minutes)
Files
Vanir: https://drive.google.com/file/d/0B7agwkTbiz0pNHZMQlpudkR4NUU/view
GAPPS: https://mega.co.nz/#!kokjzJwT!eqmMam5r5N2kWvtmSMy4QnaHnxvoqhDtr_joSDU5anI
MIUI
Another option is MIUI (used on the the popular Chinese Xiaomo phones). Instead of the Vanir build, this build is still being maintained. But because it's based on Vanir it has most likely has the same bugs. Never tried it because I prefer stock Android.
2nd, the connection error fix for vanir could also work for CM (vanir uses stuff from CM).
I've tried posting this in MIUI forums and haven't gotten any replies. I'll try my luck with XDA.
How do you correctly identify Redmi 2?
I've got a RM2 that has the 2014811 variant when I check it onscreen.. But I'm skeptic that it's correct. All I know is 2014811 is suppose to be a normal Redmi 2 with 1 gigs of RAM and 8 gigs of ROM. But mine's a 2 gigs RAM & 16 gigs ROM. If I'm correct, with specs like those, my RM2 is suppose to be a RM2 enchanced variant (Pro, Prime, etc). What I can't figure out is which variant is it that I'm dealing with. Another thing that I know is that the RM2 version of mine isn't the global one because I didn't buy it from an official shop, I bought it from an external distributor. The RM 2 box is written in chinese and the characters underneath the battery are full chinese (except for the S/N and IMEI). Is my RM 2 a 2014818 or 2014819? How can I find out which variant is it that I have with me.
Thank you.
2014819- Brazilian variants
2014818- Redmi 2 prime variation of 2014811
ezrawk said:
I've tried posting this in MIUI forums and haven't gotten any replies. I'll try my luck with XDA.
How do you correctly identify Redmi 2?
I've got a RM2 that has the 2014811 variant when I check it onscreen.. But I'm skeptic that it's correct. All I know is 2014811 is suppose to be a normal Redmi 2 with 1 gigs of RAM and 8 gigs of ROM. But mine's a 2 gigs RAM & 16 gigs ROM. If I'm correct, with specs like those, my RM2 is suppose to be a RM2 enchanced variant (Pro, Prime, etc). What I can't figure out is which variant is it that I'm dealing with. Another thing that I know is that the RM2 version of mine isn't the global one because I didn't buy it from an official shop, I bought it from an external distributor. The RM 2 box is written in chinese and the characters underneath the battery are full chinese (except for the S/N and IMEI). Is my RM 2 a 2014818 or 2014819? How can I find out which variant is it that I have with me.
Thank you.
Click to expand...
Click to collapse
for me device name is beneath the battery.
hopefully for you also it must be given.remove back cover and check.
wt88047 - 2014811/12/17/18/19/21
wt86047 - 2014813/816/2014112
TecnoTailsPlays said:
2014819- Brazilian variants
2014818- Redmi 2 prime variation of 2014811
Click to expand...
Click to collapse
sarath67 said:
for me device name is beneath the battery.
hopefully for you also it must be given.remove back cover and check.
Click to expand...
Click to collapse
raymond_bqg said:
wt88047 - 2014811/12/17/18/19/21
wt86047 - 2014813/816/2014112
Click to expand...
Click to collapse
Guys thanks for your replies. After intensive research, I have concluded that: yes, my device is totally a WT88047 - HM201411 - HM 2 LTE-CU (China Unicom) variant. But now I've found out something else that's got me hooked up on finding out. I'm using latest stable stock rom (MIUI 8 - 8.2.1.0), and I checked out my Mi-Account menu in settings, snooped down to devices and... My RM2P is named Redmi 2W..... So... What the heck is Redmi 2W? I've been searching here and there with no luck on finding out what a Redmi 2W is (Haven't checked the chinese sites though). Does anyone know what it is?
ezrawk said:
Guys thanks for your replies. After intensive research, I have concluded that: yes, my device is totally a WT88047 - HM201411 - HM 2 LTE-CU (China Unicom) variant. But now I've found out something else that's got me hooked up on finding out. I'm using latest stable stock rom (MIUI 8 - 8.2.1.0), and I checked out my Mi-Account menu in settings, snooped down to devices and... My RM2P is named Redmi 2W..... So... What the heck is Redmi 2W? I've been searching here and there with no luck on finding out what a Redmi 2W is (Haven't checked the chinese sites though). Does anyone know what it is?
Click to expand...
Click to collapse
what's your purpose, flashing custom roms? simply flash twrp for wt88047 and flash whichever rom you want
ezrawk said:
Guys thanks for your replies. After intensive research, I have concluded that: yes, my device is totally a WT88047 - HM201411 - HM 2 LTE-CU (China Unicom) variant. But now I've found out something else that's got me hooked up on finding out. I'm using latest stable stock rom (MIUI 8 - 8.2.1.0), and I checked out my Mi-Account menu in settings, snooped down to devices and... My RM2P is named Redmi 2W..... So... What the heck is Redmi 2W? I've been searching here and there with no luck on finding out what a Redmi 2W is (Haven't checked the chinese sites though). Does anyone know what it is?
Click to expand...
Click to collapse
shyampandey said:
what's your purpose, flashing custom roms? simply flash twrp for wt88047 and flash whichever rom you want
Click to expand...
Click to collapse
Just take a backup your current ROM by t.w.r.p before flashing ROM(if something goes wrong).
shyampandey said:
what's your purpose, flashing custom roms? simply flash twrp for wt88047 and flash whichever rom you want
Click to expand...
Click to collapse
I've got: touchscreen issues, wake up issues, twrp issues, kernel issues and proximity issues. I'm guessing even if I tell you what I'm experiencing, you won't be able to find a solution for it (please don't say I've got defective hardware, because I don't. Why? Because 3 of my friends bought the same device as mine, in the same online shop and all of them have the same issues). But even so I'll just post all of em and cross my fingers:
TWRP's bugged, needs to timeout (screen off) first before I'm able to responsively use it (touchscreen bugged, tried all latest TWRP versions, including kumajaya's old twrp builds. Touchscreen does work on several 2.8.7.0 and below versions for KK bootloader).
Any custom rom I've flashed will always face lockscreen issues (waking up device using power button leads to unresponsive and un-swipe-able touchscreen, that means I can't unlock my device, seems like it has to do with with proximity too, and please don't ask me about gestures and modified navigation buttons, because I don't use them at all: dt2w, s2w, etc).
Any custom kernel used will always lead to device not being able to wake up (pressing power button doesn't wake up the screen, stays black, have to reset device by force, still happens even though I'm using stock CPU govs *interactive* and I/O scheds *noop* not using hotplugs, doesn't change anything)
I still even face all those problems in Stock MIUI (KK or LP.. 7, 8)
Try downloading china developer ROM? Yeah. I've done that.. Even went to the Chinese download page of miui to download the exact recommended MIUI 8 C-Dev ROM for my HM 2 LTE-CU variant, and still the same bugs occur.
Xposed? I've experimented using stock and custom roms (below API 24) that are Un-Xposed. They still exhibit the same problems as above.
Clean flash dirty flash? I totally understand what those are.
Wipe dalvik cache and cache.. Don't even dare ask about those.
Fix Permissions? Yeah.. It didnt make a difference..
Post dmseg and logcats? Trust me, you devs will probably mark my device as a different type of WT8847 (and by saying that means even if you succeed to find the problems, to fix them means you gotta totally change the 'insides' of roms and stuff to make it compatible with mine. It'll probably be a waste of time if I post those 2 guys here.
Can you help me, bro?
raymond_bqg said:
Just take a backup your current ROM by t.w.r.p before flashing ROM(if something goes wrong).
Click to expand...
Click to collapse
Yeah, I know where you're getting at bro. Let me ask you this, does it not annoy you to death when you're restoring the same backup ROMs frequently just because suddenly your device can't use wi-fi (bugged) or tether, or maybe one of the issues above occur and you just gotta try your best to keep it 'clean'.. again.. and again.. and again? I just need a damn good daily driver without issues for crying out loud :cyclops:
ezrawk said:
I've got: touchscreen issues, wake up issues, twrp issues, kernel issues and proximity issues. I'm guessing even if I tell you what I'm experiencing, you won't be able to find a solution for it (please don't say I've got defective hardware, because I don't. Why? Because 3 of my friends bought the same device as mine, in the same online shop and all of them have the same issues). But even so I'll just post all of em and cross my fingers:
TWRP's bugged, needs to timeout (screen off) first before I'm able to responsively use it (touchscreen bugged, tried all latest TWRP versions, including kumajaya's old twrp builds. Touchscreen does work on several 2.8.7.0 and below versions for KK bootloader).
Any custom rom I've flashed will always face lockscreen issues (waking up device using power button leads to unresponsive and un-swipe-able touchscreen, that means I can't unlock my device, seems like it has to do with with proximity too, and please don't ask me about gestures and modified navigation buttons, because I don't use them at all: dt2w, s2w, etc).
Any custom kernel used will always lead to device not being able to wake up (pressing power button doesn't wake up the screen, stays black, have to reset device by force, still happens even though I'm using stock CPU govs *interactive* and I/O scheds *noop* not using hotplugs, doesn't change anything)
I still even face all those problems in Stock MIUI (KK or LP.. 7, 8)
Try downloading china developer ROM? Yeah. I've done that.. Even went to the Chinese download page of miui to download the exact recommended MIUI 8 C-Dev ROM for my HM 2 LTE-CU variant, and still the same bugs occur.
Xposed? I've experimented using stock and custom roms (below API 24) that are Un-Xposed. They still exhibit the same problems as above.
Clean flash dirty flash? I totally understand what those are.
Wipe dalvik cache and cache.. Don't even dare ask about those.
Fix Permissions? Yeah.. It didnt make a difference..
Post dmseg and logcats? Trust me, you devs will probably mark my device as a different type of WT8847 (and by saying that means even if you succeed to find the problems, to fix them means you gotta totally change the 'insides' of roms and stuff to make it compatible with mine. It'll probably be a waste of time if I post those 2 guys here.
Can you help me, bro?
Yeah, I know where you're getting at bro. Let me ask you this, does it not annoy you to death when you're restoring the same backup ROMs frequently just because suddenly your device can't use wi-fi (bugged) or tether, or maybe one of the issues above occur and you just gotta try your best to keep it 'clean'.. again.. and again.. and again? I just need a damn good daily driver without issues for crying out loud :cyclops:
Click to expand...
Click to collapse
that's all are happening 'cause of source code modification of lineage from cyanogen which caused your device unfavorable base code modification, only thing can be done is flash stock rom, bootloader, recovery, modem, everything using fastboot.
shyampandey said:
that's all are happening 'cause of source code modification of lineage from cyanogen which caused your device unfavorable base code modification, only thing can be done is flash stock rom, bootloader, recovery, modem, everything using fastboot.
Click to expand...
Click to collapse
So in other words "bye-bye" to custom roms right? I'm in latest stable global miui 8 btw (LP), I clean flashed it via download mode, those problems still show up though. Okay let me just try to flash miui via fastboot or download mode again.
ezrawk said:
So in other words "bye-bye" to custom roms right? I'm in latest stable global miui 8 btw (LP), I clean flashed it via download mode, those problems still show up though. Okay let me just try to flash miui via fastboot or download mode again.
Click to expand...
Click to collapse
yeah, after problem bring fixed completely, you can come back to custom roms.
Hi, I bought an used 2014817 unit, the owner said that he has replaced the touchscreen before
The weird thing is, the latest twrp doesnt always register my touch, most of the time, I tap the screen without any reaction from the twrp, but sometimes it works, it can register my tap easily
While the previous twrp 2.8.7, didnt have this problem at all
How to fix this ? Bad drivers ?
Try flashing miui fastboot rom....it will fix the broken drivers...
Paleskin said:
Hi, I bought an used 2014817 unit, the owner said that he has replaced the touchscreen before
The weird thing is, the latest twrp doesnt always register my touch, most of the time, I tap the screen without any reaction from the twrp, but sometimes it works, it can register my tap easily
While the previous twrp 2.8.7, didnt have this problem at all
How to fix this ? Bad drivers ?
Click to expand...
Click to collapse
Yeah, the replaced touchscreen must be a replica. So bad drivers should be the case. If there's an official xiaomi agent near you, you should ask them to replace it or try finding an original touchscreen for RM2.
I'm guessing you've been facing frequent SoD's (Screen of Death that makes you have to force reboot the device) and unresponsive touchscreen when the device is trying to wake from sleep (ex: pressing power button). SoD's occurs because of the proximity sensor that is attached to the replica screen is buggy.
I used to have the same problems, but it got fixed. I bought a dead original Redmi 2 and right away I started switching parts from the dead redmi 2 to my redmi 2. Salvaging parts that I've tested and arent using right now, and replacing bad parts. Extra info: RM 2's Touchscreen isn't sold by piece. You gotta buy the whole package, from LCD to TS and Proximity.
Try reading an old ROM thread by @ketut.kumajaya (CM 12.1-13), there you'll find tons of information about buggy parts of your redmi 2. Starting from eMMC to Proximity sensors, because RM 2 are sometimes shipped with different parts inside it.
and one more thing, your thread should be posted in Q&A section, just reminding you mate!
Good luck!
So my best option right now is to go back to miui based custom rom and twrp 2.8.7, since I encountered no errors with them, thankz very much mate
Paleskin said:
So my best option right now is to go back to miui based custom rom and twrp 2.8.7, since I encountered no errors with them, thankz very much mate
Click to expand...
Click to collapse
By all means yes if you don't have the leisure to do what I just posted (Changing your replica screen to an original RM2 screen). If you do plan on using MIUI based ROM, I suggest you to sneak a peek at xiaomi.eu and download the latest rom for Redmi 2 (running MIUI 8.2 with LP-bootloader). Best performance for MIUI.
Or if you are the 1 GB RAM variant of RM2, Try going for Kitkat MIUI 8 (with KK bootloader). I'll be praying that SoD's and other bugs won't occur while you're on KK and using that replica screen of yours.
I've been on this phone for a year, and at last when I fixed it (with the methods in my last post), I fully unlocked all customization for RM2, please do consider my methods if you are going to settle with RM 2 for a while or you're facing the same bugs that I used to.
Good luck!
ezrawk said:
By all means yes if you don't have the leisure to do what I just posted (Changing your replica screen to an original RM2 screen). If you do plan on using MIUI based ROM, I suggest you to sneak a peek at xiaomi.eu and download the latest rom for Redmi 2 (running MIUI 8.2 with LP-bootloader). Best performance for MIUI.
Or if you are the 1 GB RAM variant of RM2, Try going for Kitkat MIUI 8 (with KK bootloader). I'll be praying that SoD's and other bugs won't occur while you're on KK and using that replica screen of yours.
I've been on this phone for a year, and at last when I fixed it (with the methods in my last post), I fully unlocked all customization for RM2, please do consider my methods if you are going to settle with RM 2 for a while or you're facing the same bugs that I used to.
Good luck!
Click to expand...
Click to collapse
Nah, I done wasting money on r2, I was in minovo cusrom kitkat before, and no problem encountered, so I'll just go back to minovo then, thanks
Paleskin said:
Hi, I bought an used 2014817 unit, the owner said that he has replaced the touchscreen before
The weird thing is, the latest twrp doesnt always register my touch, most of the time, I tap the screen without any reaction from the twrp, but sometimes it works, it can register my tap easily
While the previous twrp 2.8.7, didnt have this problem at all
How to fix this ? Bad drivers ?
Click to expand...
Click to collapse
Try this TWRP
https://www.androidfilehost.com/?fid=745425885120756050
nadifzidane said:
Try this TWRP
https://www.androidfilehost.com/?fid=745425885120756050
Click to expand...
Click to collapse
Works perfectly, thanks
You got any fix for sod issue on lineage 14.1 too ?
nadifzidane said:
Try this TWRP
https://www.androidfilehost.com/?fid=745425885120756050
Click to expand...
Click to collapse
Hi, where have you seen this link? I would like to learn more about the source of this TWRP before flashing it.