Related
As the title suggests, I have a Nexus S i9023 (no root, perfectly clean) and the major problem is that i've upgrade the phone to ICS manually and now there are some things that don't work (recovery, light sensor, etc.). I know that there are a lot of threads like this, i know that the problem of the recovery is a problem of brightness, but i wanna know which ROM i've to flash. I'm using the build IML74K.
Another problem is that sometimes the keyboard freezes. Is it caused by the wrong build?
Which rom did you flash?
Try lastest version of ics
I'm using ICS 4.0.3, build IML74K, flashed manually.
Sent from my Nexus S using XDA App
alfax21 said:
I'm using ICS 4.0.3, build IML74K, flashed manually.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I am using the same on my i9023 with no issues, only difference is I am rooted and have clockwork recovery. I suggest a re flash.
I'll try to re-flash the same ROM. If it won't work i'll root the phone and i'll flash CM9.
Anyway, how can i solve the problem of the keyboard? I don't think it's a problem of the build.
I've flashed the ROM for Nexus S i9023 two times but the problems still remain. Any suggestion?
alfax21 said:
I've flashed the ROM for Nexus S i9023 two times but the problems still remain. Any suggestion?
Click to expand...
Click to collapse
Only thing I can suggest is installing clockwork recovery, rooting etc and flashing another rom to see if the problem persists, if so then it probably a hardware issue.
Also where did you get the rom your flashing? There is a thread in the general section with the full rom package I used. Its on the first page at the mo.
Ok maybe there's no solution (i'm new in this forum so i can't post link as the one below):
code.google.com/p/android/issues/detail?id=23065&can=1&q=ics%20nexus%20s%20i9023%20recovery&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars
So I think it will be fixed in the next release. I ask confirmation if someone knows something.
CONTACTMC said:
Also where did you get the rom your flashing? There is a thread in the general section with the full rom package I used. Its on the first page at the mo.
Click to expand...
Click to collapse
Yeah, i've seen it. This one, right?
forum.xda-developers.com/showthread.php?t=1445635
alfax21 said:
Yeah, i've seen it. This one, right?
forum.xda-developers.com/showthread.php?t=1445635
Click to expand...
Click to collapse
Yeah that's the one, flash the full rom package. You may just have a corrupt .zip.
Alredy done two times, but the problem remains. Mmmh i don't think it's a corruption problem, i mean, i've tried to put the update in the phone from two PC.
Sent from my Nexus S using XDA App
Recovery: Known problem. Backlight stays off. Nothing you can do without unlocking your bootloader or rooting. Angle + lamp will show you what is on the screen.
Light Sensor: It's still buggy. With the phone locked, cover your hand over the light sensor (left of the ear piece while facing the phone). Hand still covering, unlock the phone. After a few seconds, remove your hand and face it under a light source. What i've noticed is it'll get brighter initially but refuse to darken again. Of course, you need to have Automatic brightness adjustment (just in case it isn't set to auto).
Unsure about your keyboard problem though, but it does like to stay open for longer than i'd like after going back to the home screen.
Harbb said:
Unsure about your keyboard problem though, but it does like to stay open for longer than i'd like after going back to the home screen.
Click to expand...
Click to collapse
Yeah, it remains open also after going back to the home screen, and it doesn't work. The only way is to crash it by going to the setting of the keyboard in the notifications.
alfax21 said:
Yeah, it remains open also after going back to the home screen, and it doesn't work. The only way is to crash it by going to the setting of the keyboard in the notifications.
Click to expand...
Click to collapse
Mine doesn't remain open though,. It just stays for say half a second, then animates away. Would be much more perfected if it went away while animating the previous window away, not a second later. I've not experienced the keyboard causing those kind of problems.
Might be wise to try SwiftKey or some other kind of keyboard alternative? That is easily enough to sway me away from stock.
Harbb said:
That is easily enough to sway me away from stock.
Click to expand...
Click to collapse
I agree. I'll wait for an Experimental Mod of CM9, then i'll root the phone.
Ok i'll make the thread as solved. I want to thanks Harbb for his help, i quote his post for those who will read this thread.
Harbb said:
Recovery: Known problem. Backlight stays off. Nothing you can do without unlocking your bootloader or rooting. Angle + lamp will show you what is on the screen.
Light Sensor: It's still buggy. With the phone locked, cover your hand over the light sensor (left of the ear piece while facing the phone). Hand still covering, unlock the phone. After a few seconds, remove your hand and face it under a light source. What i've noticed is it'll get brighter initially but refuse to darken again. Of course, you need to have Automatic brightness adjustment (just in case it isn't set to auto).
Click to expand...
Click to collapse
If you have problems (like the recovery one and the light sensor) with ICS 4.0.3, build IML74K, on your Nexus S i9023 there's nothing you can do, probably Google will fix it on his next update 4.0.5.
I'll just add that many custom ROMs allow light sensor manipulation. I hear there are great, working settings, its just the stock calibration that sucks. I've not tried this myself, but should be available in cm9, cna, etc.
..
Election Day said:
This is how I have my i9023 set up. These settings work very well, so feel free to use them.
Click to expand...
Click to collapse
Are these settings of the stock ROM?
..
Anyone have any problems like this. GPS don't work, camera don't work, gyroscope don't work, and proximity sensor don't work. I've flashed to stock and various ROMs. I'm really hoping it isn't a hardware problem.
rms13515 said:
Anyone have any problems like this. GPS don't work, camera don't work, gyroscope don't work, and proximity sensor don't work. I've flashed to stock and various ROMs. I'm really hoping it isn't a hardware problem.
Click to expand...
Click to collapse
More info would be really helpful to anyone. What rom? Are you rooted?
aooga said:
More info would be really helpful to anyone. What rom? Are you rooted?
Click to expand...
Click to collapse
Unlocked bootloader, rooted and running cm10. I replaced the screen, but I remember most of the sensors working after relacing it. Vibrate worked and auto rotate sill worked. Then soon after, I noticed all that stoped working. Doesn't matter what rom, kernel, or even if I odin to stock. I fear the worst
I got ipega 9055 game controller and noticed moving keys don't right. Keys get stuck or not register. Controller works in other phones.
This problem seems to be in other lenovo phones also.
I found some other people have similar issues:
https://forums.lenovo.com/t5/forums/v3_1/forumtopicpage/board-id/lp05_en/thread-id/923/page/2
In lenovo forums fix seems to be changing region to RU what seems weird. I have not tried this yet.
I was thinking does anyone else have game controller and issues like this?
Yes I do! And it drives me nuts trying to play Mario Kart. ?
Been trying everything to fix it...
titaniumfish said:
Yes I do! And it drives me nuts trying to play Mario Kart. ?
Been trying everything to fix it...
Click to expand...
Click to collapse
I'm going to flash custom rom because of this. I tried everything i can think of with no result..
This issue has been pretty long and Lenovo is probably not going to do anything about it.
It would be nice to know if problem persists in custom rom. I strongky think its software related but i will see after 14 days...
Been tempted to stay clear of rooting this one for the likes of sky go and android pay so let me know how you get on with the flash. See if it helps. I was checking the Bluetooth specs on my P2 compared to other devices and it doesn't seem to be that. So I'm stumped. It appears the joystick is the only thing not responding properly. One press and it appears to be stuck in that position. I know for a fact it's not the joystick. Works a treat on my old S5.
titaniumfish said:
Been tempted to stay clear of rooting this one for the likes of sky go and android pay so let me know how you get on with the flash. See if it helps. I was checking the Bluetooth specs on my P2 compared to other devices and it doesn't seem to be that. So I'm stumped. It appears the joystick is the only thing not responding properly. One press and it appears to be stuck in that position. I know for a fact it's not the joystick. Works a treat on my old S5.
Click to expand...
Click to collapse
I also wanted to stay stock for awhile longer..
Im also positive there is nothing wrong with my gamepad, tested mine with S6.
I let you know how it goes.
I can tell you now that nothing's wrong with your gamepad. In the MegaN64 app there's an option in input, controller, controller diagnostics to check the button and directional pushes. As you can see from the first screenshot the left joystick pushed down (AXIS-Y) is stuck on +0.67. Somewhere between half and a whole push. I had released the joystick while I took this screenshot. It's just stuck there. In the second screenshot I pushed the right trigger button (AXIS_GAS) Which cancelled the stuck joystick position but then that trigger button got stuck on +0.40. Nearly half a push. I had also let go of the trigger button while I took this screenshot. Personally I think it's down to Lenovo using cheap Bluetooth hardware. That's my guess. I'd love to be proved wrong though.
titaniumfish said:
I can tell you now that nothing's wrong with your gamepad. In the MegaN64 app there's an option in input, controller, controller diagnostics to check the button and directional pushes. As you can see from the first screenshot the left joystick pushed down (AXIS-Y) is stuck on +0.67. Somewhere between half and a whole push. I had released the joystick while I took this screenshot. It's just stuck there. In the second screenshot I pushed the right trigger button (AXIS_GAS) Which cancelled the stuck joystick position but then that trigger button got stuck on +0.40. Nearly half a push. I had also let go of the trigger button while I took this screenshot. Personally I think it's down to Lenovo using cheap Bluetooth hardware. That's my guess. I'd love to be proved wrong though.
Click to expand...
Click to collapse
Thanks for testing.
I really hope its not hardware problem.
I'm sad that this is pretty common problem with Lenovo phones and there is no support from their part.
How did you get on with the flash?
Any custom ROMS have any better result?
titaniumfish said:
How did you get on with the flash?
Any custom ROMS have any better result?
Click to expand...
Click to collapse
I have not yet flashed because of waiting period. Still 8 days remaining.
But in dev section i got answer that custom rom will fix issue.
Please check here: https://forum.xda-developers.com/showthread.php?t=3592706
page 4 #38
Then again I suppose there's no Knox counter on P2 haha. I'm assuming you can unroot if necessary?
Are you going to install that custom ROM in the link? Or another?
No knox counter but OEM lock what you can unlock from dev settings(waiting time 14 days). After that you loose warranty.
I was thinking to try AOSP extended(same as link) but i have not decided.
I suppose you can unroot and go back to stock but warranty is gone.
edit: Now im on Resurrection mod. No problem with bt controller what so ever.
Kiryo24 said:
No knox counter but OEM lock what you can unlock from dev settings(waiting time 14 days). After that you loose warranty.
I was thinking to try AOSP extended(same as link) but i have not decided.
I suppose you can unroot and go back to stock but warranty is gone.
edit: Now im on Resurrection mod. No problem with bt controller what so ever.
Click to expand...
Click to collapse
I was going to update anyone else on stock ROM. Just received a Gamesir WIRED controller and it's STILL experiencing the same issues. So after all that it's not been a Bluetooth issue at all. Just software. Great news that the Custom ROM worked for you. Think I might have to go down the same route. Which ROM was it you went for?
titaniumfish said:
I was going to update anyone else on stock ROM. Just received a Gamesir WIRED controller and it's STILL experiencing the same issues. So after all that it's not been a Bluetooth issue at all. Just software. Great news that the Custom ROM worked for you. Think I might have to go down the same route. Which ROM was it you went for?
Click to expand...
Click to collapse
https://forum.xda-developers.com/lenovo-p2/development/7-1-1-resurrection-remix-v5-8-2-lenovo-t3575669
Ah that would explain why my Drone was acting crazy yesterday when I was flying it with my USB Gamepad, I thought the gamepad was shot ! It never crossed my mind that the P2 might be at fault...oh well a few more days to wait before I can unlock it.
I wonder if they'll just ever release Nougat for it? Haha. They're slacking big time.
btw if there is still people using stock system and want issue fixed, Lenovo has asked me for log info. I couldn't wait and flashed custom rom. Here is thread link if anyone is interested:https://forums.lenovo.com/t5/P2-P2a42-Smartphones/bluetooth-controller-problem/td-p/3652943
Nice one, Kiryo. I'm still on stock for Android pay as it's come in so handy. ? Already had developer options enabled as I thought there might be an extra Bluetooth setting to adjust to try and fix the issue but there wasn't. So I've enabled bugging reports now. I'll send them a report over as soon as I get the controller connected later on. ?
Kiryo... Just curious. How are you getting on with the Custom ROM? Does it still have the same features the stock ROM has? Such as VR mode and dual app mode? Cheers...
titaniumfish said:
Kiryo... Just curious. How are you getting on with the Custom ROM? Does it still have the same features the stock ROM has? Such as VR mode and dual app mode? Cheers...
Click to expand...
Click to collapse
Well there is all that i need. I have no need for VR mode but i guess it works in apps normally.
I also dont use dual app mode but i guess there is mutitasking option there.
Custom roms offer much more configurations than stock.
Im overall happy. There is still some issues with volume echoing with speaker and volume sliders during call etc.. but nothing too serious.
I'm just happy with functional bt controller.
Yeah I bet. Thanks for the info. ?
I'll look into making a nand backup as well I think. (If that still exists)
Hello, so i had my OnePlus one for a while and just recently i dropped it lucky the screen didn't crack and opens up just fine but the touch stopped working is there a fix for this? And how do i go about it.. I'm currently in Egypt so there isn't really any replacements and anyone who knows much about this device to be able to repair it at a decent price. I would like to fix it on my own, and i honestly hope its just a wire unplugged or something..
Thanks.
Rexee said:
Hello, so i had my OnePlus one for a while and just recently i dropped it lucky the screen didn't crack and opens up just fine but the touch stopped working is there a fix for this? And how do i go about it.. I'm currently in Egypt so there isn't really any replacements and anyone who knows much about this device to be able to repair it at a decent price. I would like to fix it on my own, and i honestly hope its just a wire unplugged or something..
Thanks.
Click to expand...
Click to collapse
hi firstly tell me what trouble shooting have you done and secondly what rom are you on is it stock or custom
kallum7 said:
hi firstly tell me what trouble shooting have you done and secondly what rom are you on is it stock or custom
Click to expand...
Click to collapse
I was on a Custom rom i forgot the name but i think it was Tuga its been a while since i last used the phone due to the issue. But the touch screen didn't work in recovery either.
Rexee said:
I was on a Custom rom i forgot the name but i think it was Tuga its been a while since i last used the phone due to the issue. But the touch screen didn't work in recovery either.
Click to expand...
Click to collapse
please follow this https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 and when it says it is only for hard bricks a=only still use it
Rexee said:
Hello, so i had my OnePlus one for a while and just recently i dropped it lucky the screen didn't crack and opens up just fine but the touch stopped working is there a fix for this? And how do i go about it.. I'm currently in Egypt so there isn't really any replacements and anyone who knows much about this device to be able to repair it at a decent price. I would like to fix it on my own, and i honestly hope its just a wire unplugged or something..
Thanks.
Click to expand...
Click to collapse
If you're screen stopped working after dropping it, it is most likely damaged. Dropping it will not cause any rom to malfunction and stop touch from working. It may be a loose connection, or if you got the device used from somewhere, the screen may have once been replaced and the replacement may not be as good as the original (which by no means was perfect either).
It happened to me. Open your opo, disconnect and then reconnect the screen.
Hello guys, i just bought this device a couple of days ago, for just 49.900 KWD = less than 150 USD, for its specs this is a steal.
Anyways, the device is awesome , but the development is dead, whats going on here.
I had poco f1 back on 2018 and it's development is going on.
Now i have poco f2 pro, but i liked the u12+ design.
The problem is the battery doesn't last 4 hours of sot during the day!
Is there any solution for it?
lol, me too Mostafa, i bought mine from FCC for 49KD
I unlocked the bootloader and flashed the beta viper rom, android 11
battery is the same, it's how it was built, it never lasts longer than 4hrs sot, but im hoping it will be improved once the viper rom goes into stable release
if you need any help you can pm me your phone number
Hahahahahahah.
The device is awesome bro, i unlocked and rooted too, but checked viper and read it has some issues, can u tell me your experience.
As i want to use the device as my main daily driver.
mostafa asal said:
Hahahahahahah.
The device is awesome bro, i unlocked and rooted too, but checked viper and read it has some issues, can u tell me your experience.
As i want to use the device as my main daily driver.
Click to expand...
Click to collapse
You can def use it as a main driver, get Viper, it's great.
If you check the last page in there or perior, i posted a reply mentioning few bugs, and most of them i fixed, rest are minor bugs that wont affect your usage that much, hence why i said once stable is out, the rom will be amazing
PS: What are you using right now if you dont mind me asking ? Stock n rooted ?
Yup stock and rooted.
I will try it today , thanks a lot bro
managed to flash it after a couple of failed tries an hour ago.
first impression >> amaaaaaazing.
mostafa asal said:
managed to flash it after a couple of failed tries an hour ago.
first impression >> amaaaaaazing.
Click to expand...
Click to collapse
Mostafa, did you perm-flash TWRP & root after flashing Viper Beta ? If yes can you please PM me with the steps you followed ?
Inpain said:
Mostafa, did you perm-flash TWRP & root after flashing Viper Beta ? If yes can you please PM me with the steps you followed ?
Click to expand...
Click to collapse
Mmmmm okey , i'm really not sure cuz i flashed the rom 3 timed till now, and every time it worked with a different order of steps
But the last time which i fell it more stable.
-Booted twrp
-Adb pushed all the files and fixes i needed.
even the system.img as i don't know why it never worked for me to flash it from download mode.
- flashed twrp img then magisk 21.1
as the newer version cuzed bootloop for me( idk i might be wrong and the reason is something else)
- flashed all the fixes i wanted.
-Entered download mode erased userdata, system.
-Rebooted to recovery
- flashed system.img and gapps.
- rebooted
- never really cared about cts so haven't done it's fix.
Anyways cbk app and kuwait id app always detect root even after activating hide in magisk
Last thing the only way i found to get ytvanced working is to flash the old magisk module for it.
Old but better than not working at all.
Have you found a fix for auto rotate, and the broken auto brightness or the in calls bluetooth headsets?
mostafa asal said:
Have you found a fix for auto rotate, and the broken auto brightness or the in calls bluetooth headsets?
Click to expand...
Click to collapse
Auto-rotate isnt broken, just goto settings > Edge Sense > Holding gesture & turn off Smart rotate
As for the Auto Brightness, i never had an issue with it, what's your issue ?
Bluetooth is working fine for me if i connect through the AUX BT dongle that i have in my car, never tested headsets.
Inpain said:
Auto-rotate isnt broken, just goto settings > Edge Sense > Holding gesture & turn off Smart rotate
As for the Auto Brightness, i never had an issue with it, what's your issue ?
Bluetooth is working fine for me if i connect through the AUX BT dongle that i have in my car, never tested headsets.
Click to expand...
Click to collapse
yup, you're right about the auto rotate.
but i have a very strange behavior regarding auto brightness, may be the rom needs one more time flashing, lol.
cuz each time i flash it , it gets more stable.
mostafa asal said:
yup, you're right about the auto rotate.
but i have a very strange behavior regarding auto brightness, may be the rom needs one more time flashing, lol.
cuz each time i flash it , it gets more stable.
Click to expand...
Click to collapse
That does not answer my question what is the auto-brightness issue you're facing ?
Also, re-flashing the ROM multiple times isn't going to make it stable-ER
Inpain said:
That does not answer my question what is the auto-brightness issue you're facing ?
Also, re-flashing the ROM multiple times isn't going to make it stable-ER
Click to expand...
Click to collapse
the issue i have is the auto brightness is uncontrollable, sometimes it reaches it's peak and never cool down, and once you lower it down manually, it never goes up !
there's a certain point it operate within , even when i slide it below this point it goes to zero again.
i will upload a vid for it.
mostafa asal said:
Click to expand...
Click to collapse
I see, well you can try something, go back to stock, and see if it behaves the same, if it does, then your sensors aren't working and you'll need to take it to FCC, just make sure you re-lock it before you do so
If it's normal on stock, then yeah, it's a ROM issue.
For me, not being able to use CBK & the Civil-ID app is a huge deal breaker, i'm going to return it back to stock and sell it, and just use my Xiaomi Mi10T 5G PRO again
Inpain said:
I see, well you can try something, go back to stock, and see if it behaves the same, if it does, then your sensors aren't working and you'll need to take it to FCC, just make sure you re-lock it before you do so
If it's normal on stock, then yeah, it's a ROM issue.
For me, not being able to use CBK & the Civil-ID app is a huge deal breaker, i'm going to return it back to stock and sell it, and just use my Xiaomi Mi10T 5G PRO again
Click to expand...
Click to collapse
On stock it works perfect, so there's no issue with the sensor.
The bad thing about this device if you relocked it. It says ( relocked ), they will know anyway.
Unlike my poco f2 pro, before i sent it to blooms for cleaning the speaker, i had to relock it, and it says locked.
Why htc made such thing!!
Yesterday, i was in Fahahel and i found FFC store and asked them about a cover and screen protector for the device, they said they don't have!!!
They are the only one selling the device in kuwait and they don't have covers for it.
But if you dying for it they can import it from UAE for 7 KWD
It to
Inpain said:
For me, not being able to use CBK & the Civil-ID app is a huge deal breaker, i'm going to return it back to stock and sell it, and just use my Xiaomi Mi10T 5G PRO again
Click to expand...
Click to collapse
Maybe if you waited for the stable rom, thay can solve the issue, or maybe there's a workaround.
For me i'm using it as a secondary device for music n videos.
And it's elegant design and color.