Related
Hi all! I just purchased 4 days ago my nexus 4 16Gb
Im quite happy with it but here are some questions: I'm just asking them because probably someone else has already gone through the same doubts and probably has some more experience: This device's forums have the fame of being more polite and tolerant than some other, so I hope you guys give me some feedback
I come from SGSII - I have ben using CM9 and 10.0 until it got bricked on november 2012
In the moment i received the new phone, i unlocked it, installed CWM Recovery and made a backup of the original ROM, then, installed CM10.1+franco kernel (both nightly)
The questions I have are:
1: Perhaps the low battery life has something to do with the fact that this is my new toy and I cannot stop playing with it, but I'm thinking about trying official ROM+ root.... would this improve the battery life?
2: The camera has been acting weird a couple of times: Once, the image was flickering: a reboot fixed it.... and another time, when i opened the camera app, would get a black screen. Im not very patient.... so I restarted and the problem is gone... Would official ROM fix this?
3: Which features do we have in stock rom that are not present on CM?
4: On stock rom, can you Root/Unroot and then re-lock the phone as if nothing happened? ¿Do you lose data if you do so?
5: There is a lot of confusion about this: When you unlock the phone, the disclaimer says that process "MIGHT" VOID THE WARRANTY..... does it void it or not?, what does that "might" mean?
Overall, the phone is wonderful and I'm really happy, I'm just thinking about testing stock rom but I don't want to lose functionality...
I'm waiting for your advice.
Thanks!!
GFXi0N said:
Hi all! I just purchased 4 days ago my nexus 4 16Gb
Im quite happy with it but here are some questions: I'm just asking them because probably someone else has already gone through the same doubts and probably has some more experience: This device's forums have the fame of being more polite and tolerant than some other, so I hope you guys give me some feedback
I come from SGSII - I have ben using CM9 and 10.0 until it got bricked on november 2012
In the moment i received the new phone, i unlocked it, installed CWM Recovery and made a backup of the original ROM, then, installed CM10.1+franco kernel (both nightly)
The questions I have are:
1: Perhaps the low battery life has something to do with the fact that this is my new toy and I cannot stop playing with it, but I'm thinking about trying official ROM+ root.... would this improve the battery life?
2: The camera has been acting weird a couple of times: Once, the image was flickering: a reboot fixed it.... and another time, when i opened the camera app, would get a black screen. Im not very patient.... so I restarted and the problem is gone... Would official ROM fix this?
3: Which features do we have in stock rom that are not present on CM?
4: On stock rom, can you Root/Unroot and then re-lock the phone as if nothing happened? ¿Do you lose data if you do so?
5: There is a lot of confusion about this: When you unlock the phone, the disclaimer says that process "MIGHT" VOID THE WARRANTY..... does it void it or not?, what does that "might" mean?
Overall, the phone is wonderful and I'm really happy, I'm just thinking about testing stock rom but I don't want to lose functionality...
I'm waiting for your advice.
Thanks!!
Click to expand...
Click to collapse
Thread allready excists:
https://www.google.nl/url?sa=t&rct=...O-GpCSO_eYYCvy4ortY3ZoQ&bvm=bv.44158598,d.d2k
There are tons of these threads, no need to post yet another one and don`t wait on other users yo answer YOUR question. Google and search XDA please.
Hello
I recently installed my first rom - SlimBean 4.3.1 bulid 2.2
The rom works fine but after 1 week i noticed my battery start to drain very quickly.
I check with GSam Battery Monitor and i found out that *kernel* eat most of my battery.
I want to change the kernel.
which kernel will save my battery in a better way?
My current kernel is: 3.0.80+
Dan
danavon said:
Hello
I recently installed my first rom - SlimBean 4.3.1 bulid 2.2
The rom works fine but after 1 week i noticed my battery start to drain very quickly.
I check with GSam Battery Monitor and i found out that *kernel* eat most of my battery.
I want to change the kernel.
which kernel will save my battery in a better way?
My current kernel is: 3.0.80+
Dan
Click to expand...
Click to collapse
Dan,
Can you give a little more information? Type of phone, which version of Android you upgraded from etc?
I can't say that I've encountered any battery drain issues with Slimbean in the past..... it's only ever helped things.
The only question I'd ask is did you follow the correct instructions when flashing? (deleting / formatting all of the cashes etc don't just do a factory reset). Your probably a very clever guy who did everything correctly - but it's the only thing I can think of.
I'd try re-flashing following the instructions on the slimbean website to the letter......
Hope this helps
MD
monkeydogger said:
Dan,
Can you give a little more information? Type of phone, which version of Android you upgraded from etc?
I can't say that I've encountered any battery drain issues with Slimbean in the past..... it's only ever helped things.
The only question I'd ask is did you follow the correct instructions when flashing? (deleting / formatting all of the cashes etc don't just do a factory reset). Your probably a very clever guy who did everything correctly - but it's the only thing I can think of.
I'd try re-flashing following the instructions on the slimbean website to the letter......
Hope this helps
MD
Click to expand...
Click to collapse
So, does this mean, there is no option to use a custom kernel for Slimean 4.3 build 2.2? I am on i9300 on Slimean 4.3 build 2.2...
Shonilchi said:
So, does this mean, there is no option to use a custom kernel for Slimean 4.3 build 2.2? I am on i9300 on Slimean 4.3 build 2.2...
Click to expand...
Click to collapse
He didn't say that. He was asking Dan did he correctly followed the installation procedures or not, because issues sometimes caused from previous rom installations leftovers (not properly wiped).
And to your question, custom kernels is just a matter of individual preference. You may install any kernel as long as they are compatible with slimroms.
Although any issues caused by other kernel shouldn't be discussed in slim threads. But if you're using stock slim kernel and having problems then you may report to the devs, but make sure that problems aren't listed on the OP's Known Issues, and also provide feedback support files such as logcats or screenshots so the devs could identify the problems right away ?
Battery drainage issues
Hello,
I have recently installed SlimBean 4.2.2 on my Xperia S.
This is my first custom ROM and my previous OS was Stock 6.2.B.1.96.
Needless to say I've rooted my phone (using DoomLord's Technique), have CWM Recovery 6.0.3.0 and Unlocked the bootloader.
I had cleared data, cache, dalvik Cache before flashing the Slim-nozomi-4.2.2.build.8-OFFICIAL.zip and Slim_Gapps.4.2.2.build.8.zip
Issues:
Heavy battery drain - I left my device overnight with all radios off (Airplane mode) and the device registered a loss of 10% in battery level [ 2 Screenshots attached ]
The GSM network radios doesn't turn on when I change the Airplane Mode toggle in Notification Bar
Unrelated - How do I use the AIO_Addons.zip and AIO_Aroma.zip?
Unrelated - Does flashing a Custom ROM mean that Google Apps won't be updated via Play Store? ( Tried once - got invalid signature error )
Steps taken to remedy this (Beginner level):
Installed WakeLockDetector app to find what's up with the ROM. Turns out Google Search had maximum wakelocks [ Attached Screengrab ], despite me Greenifying the app.
I've greenified Google Search app and couple of other network accessing apps (like feedly, pocket, FalconPro (twitter client) )
Dear XDA-ers, kindly help me remediate this issue, as I truly like the ROM..but I'm sure such issues can be solved. Otherwise It wouldn't be the stable ROM that it is.
Please let me know if any other information would be helpful.
First post here, apologies if I may have offended anyone's sensibilities.
Hey guys,
I know there are threads like this all over this forum, but as I tried everything that was described in different threads and nothing worked, i just made up a new one... sorry for that.
Some days ago my home button just stopped working for no reason. I was at the latest CyanPop nightly and apart from scanning FP, everything worked fine. The FP-Error is known to CM13 because of the drivers etc so i was aware of that.. I was getting home from work when suddenly my home-button stopped working for no reason. I thought it might be due to the custom rom etc, so i went back to OxygenOS 2.2.0 but it still didn't work out.
What I tried for now:
full wipe
flashing Oxygen OS 2.0.2 and 2.0.3
installing stock modem, firmware, kernel rom and recovery
as OP support told me: unhide Google Search Bar
hard reboot (holding powerbutton until it reboots)
I still don't know if it's a hardware related error, but I really hope it's not. I bought my OP2 in the official OnePlus Store in Beijing when I was on holiday in China. I already got in contact with the OnePlus support, but they said there is no warranty for the OnePlus Two China Edition (can anyone confirm that..?), so i don't think they're not going to repair it, not even if i pay for it.
So, does anyone know what else I could try (software AND hardware related!)? Is there a way to buy a new FP-Sensor/Home-Button and replace it manually? Every smartphone-repair-store in my area told me that they don't have spare parts for OnePlus devices...
I really hope someone can help me with this!
Thanks in advance,
Neo
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.