Jump to content

[ROM][4.1.1][B209] AOSP MOD [28/02/2015]

Guest H3ROS

By Guest H3ROS
in Huawei Ascend G510 Development

 Share

Recommended Posts

Guest Insane93

Guest Insane93

Posted
Posted

Can i update from 09/10/2014 release to "update 13 28/02/2015" without the update of 15/01/2015? update 13 contains the update of 15/01/2015?

  • Replies 3.5k
  • Created
  • Last Reply

Popular Days

Popular Days

Popular Posts

Guest H3ROS
Guest H3ROS

About: My goal was to create a ROM that most of us wish the Y300 had of been sold with originally. I achieved that goal by converting the stock Huawei ROM back to AOSP, but I also improved some thing

Guest H3ROS
Guest H3ROS

Addons: 720p recording - http://www.any.gs/AGohR   Warning: The framerate will be low and you'll need to use a different camera app. The Google camera app won't work, but lgCamera does work.

Guest H3ROS
Guest H3ROS

I've uploaded the ROM and ROM update. It's probably best to start from fresh, but the update should be fine.   Everything should work perfectly with this update. Things will feel smoother and calls

Posted Images

Guest H3ROS

Guest H3ROS

Posted
Posted (edited)

Can i update from 09/10/2014 release to "update 13 28/02/2015" without the update of 15/01/2015? update 13 contains the update of 15/01/2015?

It doesn't, but I'll send you a private message with the update that you're missing.

And for anyone who missed my previous post due to this switching to a new page...

 

I made an error in the last few versions of the ROM it seems. I included an updated version of Exchange Services but I didn't check the minimum API. I just did after updating Gmail and found that it was set to KitKat, so currently exchange email support doesn't work and it could cause random reboots even if you don't use it.

Here's a fix that everyone should install: https://drive.google.com/file/d/0BzpRBylyuvsXSmQyUFNfWU9zS0E/

I'm uploading a revised version of the ROM and ROM update.

No wipes are needed when installing updates.

Edited by H3ROS
Guest Insane93

Guest Insane93

Posted
Posted

It doesn't, but I'll send you a private message with the update that you're missing.

And for anyone who missed my previous post due to this switching to a new page...

 

No wipes are needed when installing updates.

 

Thank you!

Guest Chronos666

Guest Chronos666

Posted
Posted

Someone tried whatsapp calls?? They work for you? Seems like the mic don't work. Problaby is because I have the port for g330. But it's strange because Skype and other voip app work without problem.

 

Whatsapp calls works perfect! 

Guest H3ROS

Guest H3ROS

Posted
Posted

Is that logged from CM10.1?

Here's the slimmed down log. I don't know the exact cause other than something audio related isn't setup correctly for the G330.

03-31 18:27:55.550 I/ActivityManager(  437): Displayed com.whatsapp/.HomeActivity: +1s310ms (total +1s505ms)
03-31 18:27:58.280 E/MM_OSAL (  154): ValidateAACFile failed
03-31 18:27:58.470 I/AudioService(  437):  AudioFocus  requestAudioFocus() from [email protected]@41b509b0
03-31 18:27:58.490 E/AudioPolicyManager7627a(  154): setPhoneState() state 3
03-31 18:27:58.610 W/AudioHardwareMSM76XXA(  154): VoipCall in MODE_IN_COMMUNICATION
03-31 18:27:58.610 W/AudioHardwareMSM76XXA(  154): rpc_snd_set_device(0, 0, 0)
03-31 18:27:59.230 I/WhatsAppJni( 9038): EnsureThreadAttached: attached current thread to JVM
03-31 18:27:59.970 E/AudioPolicyManagerBase(  154):  profile found: device 100000, flags 0, samplingrate 16000,            format 1, channelMask 16
03-31 18:27:59.970 E/AudioHardwareMSM76XXA(  154): open mvs driver
03-31 18:28:00.250 I/ActivityManager(  437): Displayed com.whatsapp/.VoipActivity: +931ms
03-31 18:28:09.980 E/AudioHardwareMSM76XXA(  154): VoipOut 0 driver fd 26
03-31 18:28:09.980 W/AudioHardwareMSM76XXA(  154): rpc_snd_set_device(2147483646, 1, 1)
03-31 18:28:10.040 E/AudioHardwareMSM76XXA(  154): VoipOut 0 driver fd -1
03-31 18:28:10.040 E/AudioHardwareMSM76XXA(  154): Not closing MVS driver
03-31 18:28:10.040 E/AudioHardwareMSM76XXA(  154): VoipOut 0 driver fd -1
03-31 18:28:10.040 E/AudioHardwareMSM76XXA(  154): Not closing MVS driver
03-31 18:28:10.160 I/WhatsAppJni( 9038): EnsureThreadAttached: attached current thread to JVM
03-31 18:28:10.220 E/AudioPolicyManagerBase(  154):  profile found: device 100000, flags 0, samplingrate 16000,            format 1, channelMask 16
03-31 18:28:10.220 E/AudioHardwareMSM76XXA(  154): open mvs driver
03-31 18:28:20.220 E/AudioHardwareMSM76XXA(  154): VoipOut 0 driver fd 34
03-31 18:28:20.240 E/AudioHardwareMSM76XXA(  154): VoipOut 0 driver fd -1
03-31 18:28:20.240 E/AudioHardwareMSM76XXA(  154): Not closing MVS driver
03-31 18:28:20.270 W/AudioHardwareMSM76XXA(  154): rpc_snd_set_device(0, 1, 1)
03-31 18:28:20.270 E/AudioHardwareMSM76XXA(  154):  reopen the device 
03-31 18:28:20.270 E/AudioHardwareMSM76XXA(  154): open mvs driver
03-31 18:28:31.280 E/AudioHardwareMSM76XXA(  154): retry read count = 640 buffersize = 640
03-31 18:28:31.280 E/AudioFlinger(  154): Error reading audio input
03-31 18:28:31.280 E/AudioHardwareMSM76XXA(  154): VoipOut 0 driver fd 34
03-31 18:28:31.280 E/AudioPolicyManager7627a(  154): newDevice after getNewDevice 1
03-31 18:28:31.280 E/AudioPolicyManager7627a(  154): stopInput 2 string to setParam routing=1
03-31 18:28:31.290 E/AudioPolicyManager7627a(  154): After set param with mPrimaryOutput
03-31 18:28:31.650 I/WhatsAppJni( 9038): EnsureThreadAttached: attached current thread to JVM
03-31 18:28:32.360 W/AudioRecord( 9038): obtainBuffer timed out (is the CPU pegged?) user=00000000, server=00000000
03-31 18:28:32.370 E/AudioHardwareMSM76XXA(  154):  reopen the device 
03-31 18:28:32.370 E/AudioHardwareMSM76XXA(  154): open mvs driver
03-31 18:28:43.370 E/AudioHardwareMSM76XXA(  154): retry read count = 640 buffersize = 640
03-31 18:28:43.370 E/AudioFlinger(  154): Error reading audio input
03-31 18:28:43.370 E/AudioHardwareMSM76XXA(  154): VoipOut 0 driver fd 35
03-31 18:28:43.370 E/AudioPolicyManager7627a(  154): newDevice after getNewDevice 1
03-31 18:28:43.370 E/AudioPolicyManager7627a(  154): stopInput 2 string to setParam routing=1
03-31 18:28:43.400 E/AudioPolicyManager7627a(  154): After set param with mPrimaryOutput
03-31 18:28:44.430 W/AudioRecord( 9038): obtainBuffer timed out (is the CPU pegged?) user=00000000, server=00000000
03-31 18:28:44.440 E/AudioHardwareMSM76XXA(  154):  reopen the device 
03-31 18:28:44.440 E/AudioHardwareMSM76XXA(  154): open mvs driver
03-31 18:28:55.440 E/AudioHardwareMSM76XXA(  154): retry read count = 640 buffersize = 640
03-31 18:28:55.440 E/AudioFlinger(  154): Error reading audio input
03-31 18:28:55.440 E/AudioHardwareMSM76XXA(  154): VoipOut 0 driver fd 35
03-31 18:28:55.440 E/AudioPolicyManager7627a(  154): newDevice after getNewDevice 1
03-31 18:28:55.440 E/AudioPolicyManager7627a(  154): stopInput 2 string to setParam routing=1
03-31 18:28:55.470 E/AudioPolicyManager7627a(  154): After set param with mPrimaryOutput
03-31 18:28:56.540 W/AudioRecord( 9038): obtainBuffer timed out (is the CPU pegged?) user=00000000, server=00000000
03-31 18:28:56.550 E/AudioHardwareMSM76XXA(  154):  reopen the device 
03-31 18:28:56.550 E/AudioHardwareMSM76XXA(  154): open mvs driver
03-31 18:28:59.400 E/MM_OSAL (  154): ValidateAACFile failed
03-31 18:29:05.720 E/MM_OSAL (  154): ValidateAACFile failed
03-31 18:29:06.320 E/MM_OSAL (  154): ValidateAACFile failed
03-31 18:29:06.590 E/MM_OSAL (  154): ValidateAACFile failed
03-31 18:29:06.780 E/MM_OSAL (  154): ValidateAACFile failed
03-31 18:29:07.310 E/MM_OSAL (  154): ValidateAACFile failed
03-31 18:29:07.470 E/MM_OSAL (  154): ValidateAACFile failed
03-31 18:29:07.550 E/AudioHardwareMSM76XXA(  154): retry read count = 640 buffersize = 640
03-31 18:29:07.550 E/AudioFlinger(  154): Error reading audio input
03-31 18:29:07.550 E/AudioHardwareMSM76XXA(  154): VoipOut 0 driver fd 35
03-31 18:29:07.550 E/AudioPolicyManager7627a(  154): newDevice after getNewDevice 1
03-31 18:29:07.550 E/AudioPolicyManager7627a(  154): stopInput 2 string to setParam routing=1
03-31 18:29:07.590 E/AudioPolicyManager7627a(  154): After set param with mPrimaryOutput
03-31 18:29:07.600 E/AudioHardwareMSM76XXA(  154): VoipOut 0 driver fd -1
03-31 18:29:07.600 E/AudioHardwareMSM76XXA(  154): Not closing MVS driver
03-31 18:29:07.600 I/WhatsAppJni( 9038): DetachThreadOnExit: detached current thread from JVM
03-31 18:29:07.630 E/MM_OSAL (  154): ValidateAACFile failed
03-31 18:29:07.660 I/WhatsAppJni( 9038): DetachThreadOnExit: detached current thread from JVM
03-31 18:29:07.780 W/AudioHardwareMSM76XXA(  154): rpc_snd_set_device(2147483646, 1, 0)
03-31 18:29:07.780 E/AudioPolicyManager7627a(  154): setPhoneState() state 0
03-31 18:29:07.800 W/MemoryDealer(  154): madvise(0x42db1000, 4096, MADV_REMOVE) returned Operation not supported on transport endpoint
03-31 18:29:07.840 I/AudioService(  437):  AudioFocus  abandonAudioFocus() from [email protected]@41b509b0
03-31 18:29:07.860 W/MemoryDealer(  154): madvise(0x435cf000, 16384, MADV_REMOVE) returned Operation not supported on transport endpoint
03-31 18:29:13.090 E/MM_OSAL (  154): ValidateAACFile failed
Guest davef7

Guest davef7

Posted
Posted

Is that logged from CM10.1?

Here's the slimmed down log. I don't know the exact cause other than something audio related isn't setup correctly for the G330.

03-31 18:27:55.550 I/ActivityManager(  437): Displayed com.whatsapp/.HomeActivity: +1s310ms (total +1s505ms)
03-31 18:27:58.280 E/MM_OSAL (  154): ValidateAACFile failed
03-31 18:27:58.470 I/AudioService(  437):  AudioFocus  requestAudioFocus() from [email protected]@41b509b0
03-31 18:27:58.490 E/AudioPolicyManager7627a(  154): setPhoneState() state 3
03-31 18:27:58.610 W/AudioHardwareMSM76XXA(  154): VoipCall in MODE_IN_COMMUNICATION
03-31 18:27:58.610 W/AudioHardwareMSM76XXA(  154): rpc_snd_set_device(0, 0, 0)
03-31 18:27:59.230 I/WhatsAppJni( 9038): EnsureThreadAttached: attached current thread to JVM
03-31 18:27:59.970 E/AudioPolicyManagerBase(  154):  profile found: device 100000, flags 0, samplingrate 16000,            format 1, channelMask 16
03-31 18:27:59.970 E/AudioHardwareMSM76XXA(  154): open mvs driver
03-31 18:28:00.250 I/ActivityManager(  437): Displayed com.whatsapp/.VoipActivity: +931ms
03-31 18:28:09.980 E/AudioHardwareMSM76XXA(  154): VoipOut 0 driver fd 26
03-31 18:28:09.980 W/AudioHardwareMSM76XXA(  154): rpc_snd_set_device(2147483646, 1, 1)
03-31 18:28:10.040 E/AudioHardwareMSM76XXA(  154): VoipOut 0 driver fd -1
03-31 18:28:10.040 E/AudioHardwareMSM76XXA(  154): Not closing MVS driver
03-31 18:28:10.040 E/AudioHardwareMSM76XXA(  154): VoipOut 0 driver fd -1
03-31 18:28:10.040 E/AudioHardwareMSM76XXA(  154): Not closing MVS driver
03-31 18:28:10.160 I/WhatsAppJni( 9038): EnsureThreadAttached: attached current thread to JVM
03-31 18:28:10.220 E/AudioPolicyManagerBase(  154):  profile found: device 100000, flags 0, samplingrate 16000,            format 1, channelMask 16
03-31 18:28:10.220 E/AudioHardwareMSM76XXA(  154): open mvs driver
03-31 18:28:20.220 E/AudioHardwareMSM76XXA(  154): VoipOut 0 driver fd 34
03-31 18:28:20.240 E/AudioHardwareMSM76XXA(  154): VoipOut 0 driver fd -1
03-31 18:28:20.240 E/AudioHardwareMSM76XXA(  154): Not closing MVS driver
03-31 18:28:20.270 W/AudioHardwareMSM76XXA(  154): rpc_snd_set_device(0, 1, 1)
03-31 18:28:20.270 E/AudioHardwareMSM76XXA(  154):  reopen the device 
03-31 18:28:20.270 E/AudioHardwareMSM76XXA(  154): open mvs driver
03-31 18:28:31.280 E/AudioHardwareMSM76XXA(  154): retry read count = 640 buffersize = 640
03-31 18:28:31.280 E/AudioFlinger(  154): Error reading audio input
03-31 18:28:31.280 E/AudioHardwareMSM76XXA(  154): VoipOut 0 driver fd 34
03-31 18:28:31.280 E/AudioPolicyManager7627a(  154): newDevice after getNewDevice 1
03-31 18:28:31.280 E/AudioPolicyManager7627a(  154): stopInput 2 string to setParam routing=1
03-31 18:28:31.290 E/AudioPolicyManager7627a(  154): After set param with mPrimaryOutput
03-31 18:28:31.650 I/WhatsAppJni( 9038): EnsureThreadAttached: attached current thread to JVM
03-31 18:28:32.360 W/AudioRecord( 9038): obtainBuffer timed out (is the CPU pegged?) user=00000000, server=00000000
03-31 18:28:32.370 E/AudioHardwareMSM76XXA(  154):  reopen the device 
03-31 18:28:32.370 E/AudioHardwareMSM76XXA(  154): open mvs driver
03-31 18:28:43.370 E/AudioHardwareMSM76XXA(  154): retry read count = 640 buffersize = 640
03-31 18:28:43.370 E/AudioFlinger(  154): Error reading audio input
03-31 18:28:43.370 E/AudioHardwareMSM76XXA(  154): VoipOut 0 driver fd 35
03-31 18:28:43.370 E/AudioPolicyManager7627a(  154): newDevice after getNewDevice 1
03-31 18:28:43.370 E/AudioPolicyManager7627a(  154): stopInput 2 string to setParam routing=1
03-31 18:28:43.400 E/AudioPolicyManager7627a(  154): After set param with mPrimaryOutput
03-31 18:28:44.430 W/AudioRecord( 9038): obtainBuffer timed out (is the CPU pegged?) user=00000000, server=00000000
03-31 18:28:44.440 E/AudioHardwareMSM76XXA(  154):  reopen the device 
03-31 18:28:44.440 E/AudioHardwareMSM76XXA(  154): open mvs driver
03-31 18:28:55.440 E/AudioHardwareMSM76XXA(  154): retry read count = 640 buffersize = 640
03-31 18:28:55.440 E/AudioFlinger(  154): Error reading audio input
03-31 18:28:55.440 E/AudioHardwareMSM76XXA(  154): VoipOut 0 driver fd 35
03-31 18:28:55.440 E/AudioPolicyManager7627a(  154): newDevice after getNewDevice 1
03-31 18:28:55.440 E/AudioPolicyManager7627a(  154): stopInput 2 string to setParam routing=1
03-31 18:28:55.470 E/AudioPolicyManager7627a(  154): After set param with mPrimaryOutput
03-31 18:28:56.540 W/AudioRecord( 9038): obtainBuffer timed out (is the CPU pegged?) user=00000000, server=00000000
03-31 18:28:56.550 E/AudioHardwareMSM76XXA(  154):  reopen the device 
03-31 18:28:56.550 E/AudioHardwareMSM76XXA(  154): open mvs driver
03-31 18:28:59.400 E/MM_OSAL (  154): ValidateAACFile failed
03-31 18:29:05.720 E/MM_OSAL (  154): ValidateAACFile failed
03-31 18:29:06.320 E/MM_OSAL (  154): ValidateAACFile failed
03-31 18:29:06.590 E/MM_OSAL (  154): ValidateAACFile failed
03-31 18:29:06.780 E/MM_OSAL (  154): ValidateAACFile failed
03-31 18:29:07.310 E/MM_OSAL (  154): ValidateAACFile failed
03-31 18:29:07.470 E/MM_OSAL (  154): ValidateAACFile failed
03-31 18:29:07.550 E/AudioHardwareMSM76XXA(  154): retry read count = 640 buffersize = 640
03-31 18:29:07.550 E/AudioFlinger(  154): Error reading audio input
03-31 18:29:07.550 E/AudioHardwareMSM76XXA(  154): VoipOut 0 driver fd 35
03-31 18:29:07.550 E/AudioPolicyManager7627a(  154): newDevice after getNewDevice 1
03-31 18:29:07.550 E/AudioPolicyManager7627a(  154): stopInput 2 string to setParam routing=1
03-31 18:29:07.590 E/AudioPolicyManager7627a(  154): After set param with mPrimaryOutput
03-31 18:29:07.600 E/AudioHardwareMSM76XXA(  154): VoipOut 0 driver fd -1
03-31 18:29:07.600 E/AudioHardwareMSM76XXA(  154): Not closing MVS driver
03-31 18:29:07.600 I/WhatsAppJni( 9038): DetachThreadOnExit: detached current thread from JVM
03-31 18:29:07.630 E/MM_OSAL (  154): ValidateAACFile failed
03-31 18:29:07.660 I/WhatsAppJni( 9038): DetachThreadOnExit: detached current thread from JVM
03-31 18:29:07.780 W/AudioHardwareMSM76XXA(  154): rpc_snd_set_device(2147483646, 1, 0)
03-31 18:29:07.780 E/AudioPolicyManager7627a(  154): setPhoneState() state 0
03-31 18:29:07.800 W/MemoryDealer(  154): madvise(0x42db1000, 4096, MADV_REMOVE) returned Operation not supported on transport endpoint
03-31 18:29:07.840 I/AudioService(  437):  AudioFocus  abandonAudioFocus() from [email protected]@41b509b0
03-31 18:29:07.860 W/MemoryDealer(  154): madvise(0x435cf000, 16384, MADV_REMOVE) returned Operation not supported on transport endpoint
03-31 18:29:13.090 E/MM_OSAL (  154): ValidateAACFile failed
No is a logcat from aosp mod ported to g330, for the port we change two lib (libcm.so and audio.primary.msm...) that a guy gave to us. I know isn't a good method to port a Rom (I'm not an expert), but it works, and whatsapp calls are the first problem for me with aosp mod.
Guest fonz93

Guest fonz93

Posted
Posted

Is that logged from CM10.1?

Here's the slimmed down log. I don't know the exact cause other than something audio related isn't setup correctly for the G330.

 

No, it's logged from an AOSP MOD port for G330, don't know where the audio libs are built, probably are similar to u8815.

Guest davef7

Guest davef7

Posted
Posted

No, it's logged from an AOSP MOD port for G330, don't know where the audio libs are built, probably are similar to u8815.

Yes, if I remember well, this guy tried many lib from devices similar to g330, and with fortune he discover one that works.

In this situation I can understand that is very difficult to resolve, so thanks to both!

I can live without whatsapp calls.

Guest H3ROS

Guest H3ROS

Posted
Posted (edited)

Well in that case try taking all of the files starting with "audio" from /system/etc/ of the latest stock G330 ROM and putting them into this ROM. If that doesn't fix it then it could be one of the libs, but it could also be linked in with the kernel much like how bluetooth headset fixes are kernel specific.

Edited by H3ROS
Guest davef7

Guest davef7

Posted
Posted

Well in that case try taking all of the files starting with "audio" from /system/etc/ of the latest stock G330 ROM and putting them into this ROM. If that doesn't fix it then it could be one of the libs, but it could also be linked in with the kernel much like how bluetooth headset fixes are kernel specific.

Ok Thanks! I will try.
Guest killadroid

Guest killadroid

Posted
Posted

Someone tried whatsapp calls?? They work for you? Seems like the mic don't work. Problaby is because I have the port for g330. But it's strange because Skype and other voip app work without problem.

works great here.tho i use whatsapp plus
Guest zic

Guest zic

Posted
Posted
Hello,
 
As AOSP MOD ROM seems to be a reference, I would like to install it to give a new life to my Y300 (my goal is just to use Gmail, Sms, and Chrome, and to have a more faster phone if possible)
 
As i am new on all these questions, could you tell me, please :
 
- a link or method to help me to ROOT my Y300
- a link or method to help me to install the AOSP MOD ROM (I understand the link to download the ROM package is : http://www.any.gs/AGoe4 on Page 1)
 
Thank you very much
 
PS : I'm sorry, i guess this question has to be asked already
PS : my Y300 has never been rooted before (build Y300-0100V100R001C00B209 France)
Guest H3ROS

Guest H3ROS

Posted
Posted

This should still work: http://huawei-y300.tumblr.com/

It'll install a TWRP recovery (hold volume up and press the power button to access). From there you should backup your stock ROM, just in case things go wrong. You can then wipe all of your partitions apart from your SD card and install AOSP MOD.

Guest Takamoto

Guest Takamoto

Posted
Posted

Hello,I have a abnormal battery drain for smsdispatcher..how can I fix it please?post-1047701-14279742598041_thumb.png

Guest noobynobita

Guest noobynobita

Posted
Posted

H3ROS,i have an issue with battery life.Sometimes when i charge it suddenly jumps from 25% or something to 90% or likewise.And even when it is switched off and i charge it,it jumps from 20% to 60%.The numbers aren't fixed. What might be the issue over here?I use greeenify and have disbaled some services.

Guest Tameem1234567890

Guest Tameem1234567890

Posted
Posted

I am just want to say that this is a GREAT Rom. It is just the rom i was looking for and wanted. Thank You @H3ROS for this rom i appreciate the effort you put in making this rom.

Guest Tameem1234567890

Guest Tameem1234567890

Posted
Posted

H3ROS,i have an issue with battery life.Sometimes when i charge it suddenly jumps from 25% or something to 90% or likewise.And even when it is switched off and i charge it,it jumps from 20% to 60%.The numbers aren't fixed. What might be the issue over here?I use greeenify and have disbaled some services.

I have the same issue but a little differently. When i charge it charges really fast like from 43 to 48% in 5 secs and when i disconnect the charger the battery drops real quick too. Not that this isn't a great rom but i hope you can find a fix H3ROS.
Guest killadroid

Guest killadroid

Posted
Posted

calibrate your battery or give it a day or 2 it will be back to normal

Guest krux3r

Guest krux3r

Posted
Posted (edited)

One question. I bought a tablet yesterday, and signed in with same Google account on it like on my phone. And from then my signal bars are grey all the time.

Any help?

Edit: So I turned off the tablet, and when it is off, signal bars on phone get blue again. I guess I'll have to use an other account on tablet.

Edit 2: And the problem is again here..

Edited by krux3r
Guest janners

Guest janners

Posted
Posted

Hi,

 

Just to say thanks again to you H3ROS for all your hard work on this ROM.  Unfortunately I lost my Y300 in Germany last weekend and already I am missing this phone and this ROM.  I''m using my old ZTE blade for now, but can anyone recommend which phone would be the next step that has good custom ROM development?  Moto G?

Guest luca020400

Guest luca020400

Posted
Posted

Hi,

Just to say thanks again to you H3ROS for all your hard work on this ROM. Unfortunately I lost my Y300 in Germany last weekend and already I am missing this phone and this ROM. I''m using my old ZTE blade for now, but can anyone recommend which phone would be the next step that has good custom ROM development? Moto G?

Moto G 2014 :)
Guest noobynobita

Guest noobynobita

Posted
Posted

calibrate your battery or give it a day or 2 it will be back to normal

what do you mean by calibrate?and this issue has been going on for weeks.Rebooted it a couple of times as well
Guest Tameem1234567890

Guest Tameem1234567890

Posted
Posted

what do you mean by calibrate?and this issue has been going on for weeks.Rebooted it a couple of times as well

Let it charge to 100% then remove the charger andpower off and then charge it to 100% while powered off. Remove the charger open the mob charge it to 100% and then again remove the charger power it off and then again charge it to 100%. Then remove the charger boot into recovery and reset battery stat (CWM has different method and TWRP has different). Then open mob charge it to 100% and then use the mob and discharge it all the and once closed open it again and discharge it again. Then once powered off charge it to 100% and that should calibrate it. Easy peasy isn't it xD

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share
Go to topic listing
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.

  I accept