Related
I'm having this problem in any ics and jb roms.
Auto rotate isn't working at all but in games,camera accelerometer works fine.
And in gb autorotate also works
please help me.
Model : Arc S
current rom: Xperia Ultimate HD 3.02
Kernel : KTG
Baseband : 77
Turning it on might help?
Settings - screen - rotate automaticly
Sent from my Xperia Arc S using xda premium
TheHaso said:
Turning it on might help?
Settings - screen - rotate automaticly
Sent from my Xperia Arc S using xda premium
Click to expand...
Click to collapse
that's the first thing i chetk after installing each n every rom.....
any other solutions ??? any patch or something that can help me ?
I tried samsung's "auto rotate hot fix" patch and advanced tools which is mentioned in this topic
http://forum.xda-developers.com/showthread.php?p=25869460
but no luck
Does it work in messages, browser, gallery?
Sent from my Xperia Arc S using xda premium
TheHaso said:
Does it work in messages, browser, gallery?
Sent from my Xperia Arc S using xda premium
Click to expand...
Click to collapse
not working : gallery album walkman etc
working only on camera to capture landscape or portrait and in temple run like games it is working
and if I put ginger bread everything works
no issue on gb
Is there anyone who can help me out ???
it7.phoenix said:
Is there anyone who can help me out ???
Click to expand...
Click to collapse
You might want to ask Jader since he developed the ROM...
僕のLT18iから送られてきた
I have the same problem on my arc s
Stock ics, locked bootloader
I have searched a lot, but couldnt fins any fix
Same Problem | Some extra Info | Help needed
it7.phoenix said:
I'm having this problem in any ics and jb roms.
Auto rotate isn't working at all but in games,camera accelerometer works fine.
And in gb autorotate also works
please help me.
Model : Arc S
current rom: Xperia Ultimate HD 3.02
Kernel : KTG
Baseband : 77
Click to expand...
Click to collapse
Well, I've got the same problem on my ArcS too. Been trying to figure it out for a few days now but no luck so far. Everything stock here, got it with GB, used the PCC to upgrade to .587 and boom, no auto rotate. Currently using Rotation Locker (off market apk) to lock the screen in landscape mode to watch movies etc but it is a pain in the bottom not having it auto.
Tools I used.
1. Advanced Tools aka AT by SCDevs (Found on GPlay)
2. ES File Explorer
3. Eroot 1014 (For testing purposes but has no effect either positive or negative on the rotate problem.)
Some of my findings and let me know if any of you facing the problem have the same things wrong on your phone(s) too.
1. On AT, it lists the devices that are there but the compass is not shown while the accelerometer is. The accelerometer is showing unusual readings, i.e. the normal reading for the z-axis listed by AT is supposed to be 9.8 m/s^2 (i.e. just gravitational acceleration) when laid on a flat surface (& x,y are both supposed to be 0) but mine shows z @ 20 m/s^2 which is the max reading that the device supports.
2. The compass device (AKM8975 IC) /sys/devices/i2c-0/0-000c does not have a symlink to the /sys/bus/12c/drivers/akm8975 folder. [The accelerometer is 0-0038 & bma150 respectively]. All the folders in /i2c-0 parent folder has a symlink "driver" to the respective in bus/i2c/drivers folder. I assume this means that there is no link to the drivers while booting up and this is causing the devices to get cranky. All the other device folders have the symlink to their respective drivers folder and all the other devices are working afaik.
[See Update at the bottom]
3.
I tried samsung's "auto rotate hot fix" patch and advanced tools which is mentioned in this topic
http://forum.xda-developers.com/show...php?p=25869460
Click to expand...
Click to collapse
Yeah, I tried that too but no go.
Like someone else mentioned on that thread, SGS2 has a completely different hardware. You can figure this out yourself (If you have root). Extract the files from the AutoRotateHotfix.zip provided in that thread. Copy the file /system/bin/sensorservice and system/lib/hw/sensors.default.so to the corresponding folders on your phone. The phone will restart automatically ( after copying only one file if you have already started AT but definitely after both). Start AT and then check the list of Sensors on the device and you'll get a completely different list compared to when the stock files were there. Incidentally with the stock files the compass was not being detected at all.
My next steps.
1. Try editing the hw_config.sh file to somehow load the driver after boot or the pre_hw_config.sh or init.rc files for pre-boot/boot process.
2. Try figure out a way to add the symlink in the /sys folders but that seems to be a no go as well since that is an in-memory file system and is automatically mounted by the kernel during boot. Which probably means any changes have to be done on the source level, too much work for auto rotate since I have the rotation locker in hand.
3. Try a different kernel and ROM combo but I'm new to this so I'll need to read up a lot on that. Flashtool for Xperia seems to have capabilities to pack the .ftf files from different ROMs together so that might be a way to go. Maybe a GB kernel and ICS ROM mashup, i don't even know if that will work at all.
Help required from your side.
Check is the stuff I've noted as faulty in my phone is also the same in your phone. While this by no means guarantees that that is in fact the source of the trouble, atleast it is a start.
Hopefully this can be resolved and we can all learn a few things on the way
Updates/Edit
The compass device (AKM8975 IC) /sys/devices/i2c-0/0-000c does not have a symlink to the /sys/bus/12c/drivers/akm8975 folder. [The accelerometer is 0-0038 & bma150 respectively].
Click to expand...
Click to collapse
Checked a ST15i Xperia Mini which has no problems with auto rotate and looks like I was right, so to speak. The Mini has the symlinks in the correct places and according to AT it has the same/similar hardware. The compass chip is AKM8975 as in the Arc S but the accelerometer is BMA250 instead of BMA150 in the Arc S. So if any of you can confirm that those symlinks are missing in your phone(s) then the source of the problem can be confirmed and maybe Sony can be updated about it for a fix, which should be simple enough considering it requires only adding a couple of symlinks. How they managed to miss out on adding them in the first place is a mystery to me as the Mini is all stock and came with the ICS .431 firmware out of the box, so no updates from GB to ICS.
sabeer.abdulla said:
Well, I've got the same problem on my ArcS too. Been trying to figure it out for a few days now but no luck so far. Everything stock here, got it with GB, used the PCC to upgrade to .587 and boom, no auto rotate. Currently using Rotation Locker (off market apk) to lock the screen in landscape mode to watch movies etc but it is a pain in the bottom not having it auto.
Tools I used.
1. Advanced Tools aka AT by SCDevs (Found on GPlay)
2. ES File Explorer
3. Eroot 1014 (For testing purposes but has no effect either positive or negative on the rotate problem.)
Some of my findings and let me know if any of you facing the problem have the same things wrong on your phone(s) too.
1. On AT, it lists the devices that are there but the compass is not shown while the accelerometer is. The accelerometer is showing unusual readings, i.e. the normal reading for the z-axis listed by AT is supposed to be 9.8 m/s^2 (i.e. just gravitational acceleration) when laid on a flat surface (& x,y are both supposed to be 0) but mine shows z @ 20 m/s^2 which is the max reading that the device supports.
2. The compass device (AKM8975 IC) /sys/devices/i2c-0/0-000c does not have a symlink to the /sys/bus/12c/drivers/akm8975 folder. [The accelerometer is 0-0038 & bma150 respectively]. All the folders in /i2c-0 parent folder has a symlink "driver" to the respective in bus/i2c/drivers folder. I assume this means that there is no link to the drivers while booting up and this is causing the devices to get cranky. All the other device folders have the symlink to their respective drivers folder and all the other devices are working afaik.
[See Update at the bottom]
3.
Yeah, I tried that too but no go.
Like someone else mentioned on that thread, SGS2 has a completely different hardware. You can figure this out yourself (If you have root). Extract the files from the AutoRotateHotfix.zip provided in that thread. Copy the file /system/bin/sensorservice and system/lib/hw/sensors.default.so to the corresponding folders on your phone. The phone will restart automatically ( after copying only one file if you have already started AT but definitely after both). Start AT and then check the list of Sensors on the device and you'll get a completely different list compared to when the stock files were there. Incidentally with the stock files the compass was not being detected at all.
My next steps.
1. Try editing the hw_config.sh file to somehow load the driver after boot or the pre_hw_config.sh or init.rc files for pre-boot/boot process.
2. Try figure out a way to add the symlink in the /sys folders but that seems to be a no go as well since that is an in-memory file system and is automatically mounted by the kernel during boot. Which probably means any changes have to be done on the source level, too much work for auto rotate since I have the rotation locker in hand.
3. Try a different kernel and ROM combo but I'm new to this so I'll need to read up a lot on that. Flashtool for Xperia seems to have capabilities to pack the .ftf files from different ROMs together so that might be a way to go. Maybe a GB kernel and ICS ROM mashup, i don't even know if that will work at all.
Help required from your side.
Check is the stuff I've noted as faulty in my phone is also the same in your phone. While this by no means guarantees that that is in fact the source of the trouble, atleast it is a start.
Hopefully this can be resolved and we can all learn a few things on the way
Updates/Edit
Checked a ST15i Xperia Mini which has no problems with auto rotate and looks like I was right, so to speak. The Mini has the symlinks in the correct places and according to AT it has the same/similar hardware. The compass chip is AKM8975 as in the Arc S but the accelerometer is BMA250 instead of BMA150 in the Arc S. So if any of you can confirm that those symlinks are missing in your phone(s) then the source of the problem can be confirmed and maybe Sony can be updated about it for a fix, which should be simple enough considering it requires only adding a couple of symlinks. How they managed to miss out on adding them in the first place is a mystery to me as the Mini is all stock and came with the ICS .431 firmware out of the box, so no updates from GB to ICS.
Click to expand...
Click to collapse
1.My compass is there in AT
my Z-axis shows 21 ( but under 'BMA150 accelerometer' it shows maximum range "9.81 m/s^2"
2.i got no symlink it the /sys/devices/i2c-0/0-000c folder
3.That didnt work for me either
still no luck guys
found something interesting
http://www.slatedroid.com/topic/374...ks-fine-but-screen-doesnt-rotate/page__st__40
post #45
but this app is for bm250 and we do have bm150 so this app isn't working.
and i found one more blog which says install GB and install ics/jb without wiping anything... i did that too but no luck.......
i found something more tempting i downloaded a app "Hi Music" and autorotate is working in this app.....
now im using xperia z jelly bean 3
and as far as auto rotate i just need landscape mode in album/gallery which can be done by playing a video(which stucks screen on landscape till screen locks)
it7.phoenix said:
still no luck guys
found something interesting
http://www.slatedroid.com/topic/374...ks-fine-but-screen-doesnt-rotate/page__st__40
post #45
but this app is for bm250 and we do have bm150 so this app isn't working.
and i found one more blog which says install GB and install ics/jb without wiping anything... i did that too but no luck.......
i found something more tempting i downloaded a app "Hi Music" and autorotate is working in this app.....
now im using xperia z jelly bean 3
and as far as auto rotate i just need landscape mode in album/gallery which can be done by playing a video(which stucks screen on landscape till screen locks)
Click to expand...
Click to collapse
there are many apps for auto rotation
u should try one
and by advanced tools
orientation sensor not detected
magnetic field sensor not detected
and on accelerometer bma150 and z axis is on 22 and maximum range 9.81 m/s^2
Sahaab said:
there are many apps for auto rotation
u should try one
Click to expand...
Click to collapse
name it brother
i'll try
it7.phoenix said:
name it brother
i'll try
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=gpc.myweb.hinet.net.RotationAnywhere
here
by the way have u tried any custom kernel?
try rotation lock adaptive
Sent from my ZL 6502 latest Pac rom using XDA Premium [HD]
yes
my bootloader is unlocked
found another app whoch is great for rotating screen
https://play.google.com/store/apps/details?id=nl.fameit.rotate_license
this can help to select apps to use landscape/portrait screen
it7.phoenix said:
yes
my bootloader is unlocked
found another app whoch is great for rotating screen
https://play.google.com/store/apps/details?id=nl.fameit.rotate_license
this can help to select apps to use landscape/portrait screen
Click to expand...
Click to collapse
Is auto rotation fixed when u use a kernel which is not based on stock?
any kernel on any GB rom(stock/custom) rotation works fine
But in any JB/ICS custom or stock roms with any kernel, auto rotate is not working
it7.phoenix said:
any kernel on any GB rom(stock/custom) rotation works fine
But in any JB/ICS custom or stock roms with any kernel, auto rotate is not working
Click to expand...
Click to collapse
Its not the problem with any ROM. Arc S seems to have different drivers than Arc.
Some lib files u need to take from ur stock rom. It used to come when I flash other device os in my pro. Then, adding few libs will solve that. Dont remember wht...
If I m not wrong, browser autorotation will go to landscape and will not come back to potrait mode... Am i correct?
Hi, I've spent some time looking @ our camera since there is no evidence of sony breaking camera or not and people seem to be doing alot of guessing, some say DRM keys some say binaries causing issues etc. Enough of guessing and lets take a look at what really is going on.
This thread will look at both improving the camera & auto focus issue along with current AOSP errors
Our camera HW =
What our device currently supports: (to be filled in)
Yes Google is working on RAW camera support (We cannot enable it for our devices)
Apparently unlocking the bootloader breaks camera?????????
Build.prop modifications:
persist.camera.feature.cac (value = 1/0) (not sure what this does yet)
persist.camera.dumpimg (stores to data/img.jpg)
persist.camera.snapshot_raw (
persist.camera.preview_raw
persist.camera.zsl_raw
persist.camera.zsl_yuv
persist.camera.opt.livepic
persist.camera.zsl.interval
persist.camera.zsl.backlookcnt
persist.camera.zsl.queuedepth
persist.camera.snapshot.number
persist.denoise.process.plates
persist.camera.snap.format
persist.capture.burst.exposures
persist.debug.set.fixedfps
persist.debug.sf.showfps
persist.camera.thermal.mode
persist.camera.mem.usecache
persist.camera.longshot.save
persist.camera.dumpmetadata
pretty much self explanatory, but will give more indepth information later on these, what to set these values to and what they do...
Installed Carbon ROM which is pretty awesome but I came across errors in general and ones that are related to camera...
General Errors:-
Kernel:
SPKDRV supply cdc-vdd-spkdrv isn't defined
timeout while setting prog bit, ETMSR: 0x0
Cache ERP
ROM:
Missing binarys
Camera Errors:-
Kernel:
AVC
ROM:
Errors - IDD-API: IDD_SET_SDATA : SEND FAILED Socket 34 Errcode 2 (No such file or directory)(IMPORTANT ERROR)
Error - QCOM_SENSOR_HAL
LIBCAMERALIGHT - Sys Interface Error (this errors can be fixed by giving it write permission)
Error from Focus detector
LIBALS-SYSALS /dev/input/uevent8 (PERMISSIONS DENIED)(IMPORTANT ERROR)
CREDMGRLIB Send/Recieve socket failure Error!! (Important) (CREDMGR_RESULT_GENERIC_ERROR
Ckb create failed
Ckb is not ready
Note:
Camera Focus Distance = Infinite???? :s
Cam parameters before param fixup is called: focus-areas=(0,0,0,0,0)
Cam Parameters after param fixup is called: focus-areas=(-510,30,-398,230,1)
The above is only to identify the current errors with AOSP, when I have more free time and hopefully an upgraded PC I will be able to compile, diagnose and hopefully fix some of these...
I have a rough idea on what is going on with the camera now, will take alot of testing and patience thank you
1080p 60fps will be released soon after more testing....
1080p 60fps:
If it was like you think, why is the camera broken just by unlocking bootloader on a stock rom? Or is it not ?
Guys, it's simple.
The problem happens just because unlocking the bootloader will zero out the DRM partition.
Then, the focuser blob calls the internal DRM authentication that actually fails because of wrong keys... and that produces unability to start a server that is responsible of the communication with the actual focuser kernel driver.
That's all.
If anyone cracks the DRM binaries by Sony to change the reply, both X-Reality or Bravia as you want to call it, AND the focuser will work.
kholk said:
Guys, it's simple.
The problem happens just because unlocking the bootloader will zero out the DRM partition.
Then, the focuser blob calls the internal DRM authentication that actually fails because of wrong keys... and that produces unability to start a server that is responsible of the communication with the actual focuser kernel driver.
That's all.
If anyone cracks the DRM binaries by Sony to change the reply, both X-Reality or Bravia as you want to call it, AND the focuser will work.
Click to expand...
Click to collapse
Why do you know it's DRM? I would say it's just the binaries, not DRM
Sent from my Xperia Z1 using xda app-developers app
cocchiararo said:
If it was like you think, why is the camera broken just by unlocking bootloader on a stock rom? Or is it not ?
Click to expand...
Click to collapse
I was thinking about that, will test it too
kholk said:
Guys, it's simple.
The problem happens just because unlocking the bootloader will zero out the DRM partition.
Then, the focuser blob calls the internal DRM authentication that actually fails because of wrong keys... and that produces unability to start a server that is responsible of the communication with the actual focuser kernel driver.
That's all.
If anyone cracks the DRM binaries by Sony to change the reply, both X-Reality or Bravia as you want to call it, AND the focuser will work.
Click to expand...
Click to collapse
krabappel2548 said:
Why do you know it's DRM? I would say it's just the binaries, not DRM
Sent from my Xperia Z1 using xda app-developers app
Click to expand...
Click to collapse
@everyone this isnt a [letshaveaguesswithnoevidence] thread... Its a [dev] thread, dev posts which include debugging/evidence will be taken seriously.
Hope you guys reach a solution soon.
Good luck.
Sent from my C6903 using Tapatalk
i wouldn't say, that the camera issue is a binary problem.
i would say it is the DRM-partition ... BUT ... i was thinking about that issue and tried a lot ... ONE thing was to flash a rooted and deodexed STOCK rom on unlocked bootloader. cam wasn't working, but that was, what i expected ... then i recovered my TA-Partition and the bootloader, the rom was bootable after that (stock kernel with stock rom, just modified) but the cam was not working ... so the TA and BL recovery hasn't fixed the cam issue ...
don't know, what exactly is the problem with the cam, but i think we have to be more focused on that, because that is one reason, why people will not flash our roms and withot people trying our roms, the bug reports will not be very much ...
so if we will be able to get the camera working, there will be much more users testing our roms and kernels on their devices and we will get better feedback.
So i think the cam is the NUMBER ONE problem of our nice devices ....
I think your initiative is something to be praised here.Maybe if more devs pitched in, you could work together on this and at least come up with a few more ideas so we have a better understanding of what's actually going on (which is a start).
I'm sure that Sony would also follow your work and I'm sure they will release a fix sooner than later (it's their flagship). I was very dissapointed by this bootloader unlocking bug and I really hope this will get fixed because I for one love this phone (been using it for a month now).
I wish you good luck in this endevour! )
DJ_Synergy said:
then i recovered my TA-Partition and the bootloader, the rom was bootable after that (stock kernel with stock rom, just modified) but the cam was not working ... so the TA and BL recovery hasn't fixed the cam issue ...
Click to expand...
Click to collapse
I did this many times and always cam worked fine. Just wipe cam data after restoring TA. And of course your TA must be backuped BEFORE first unlocking.
cocchiararo said:
If it was like you think, why is the camera broken just by unlocking bootloader on a stock rom? Or is it not ?
Click to expand...
Click to collapse
Tested, it does not work with stock rom/stock kernel on unlocked bootloader... Interesting...
kholk said:
Guys, it's simple.
The problem happens just because unlocking the bootloader will zero out the DRM partition.
Then, the focuser blob calls the internal DRM authentication that actually fails because of wrong keys... and that produces unability to start a server that is responsible of the communication with the actual focuser kernel driver.
That's all.
If anyone cracks the DRM binaries by Sony to change the reply, both X-Reality or Bravia as you want to call it, AND the focuser will work.
Click to expand...
Click to collapse
You are correct, clearly you have checked this out earlier, it is the DRM keys which isnt allowing the camera to activate, its not like the camera focus is passing wrong values, the camera doesnt function at all on focus, hw focus detector error, credmanager, looks like credmgr wants the keys but isnt receiving them so doesnt activate bravia/imageproccessor...
Methods to get this working would be...
1. Crack DRM (Difficult, I wont attempt this)
2. Kexec (delewer has been working on it and he has taken it far, in talks with him, attempting to help him whenever I can)
3. Run AOSP on stock kernel... (Anyone attempted this? Not sure... Can it be done? Most likely... (wont benefit from custom kernel e.g. Overclocking undervolting etc etc))
Best option looks to be number 2, kexec
Edit: Further testing, Lets see if I can fool the device in thinking I already have the keys...
Shaky156 said:
Tested, it does not work with stock rom/stock kernel on unlocked bootloader... Interesting...
You are correct, clearly you have checked this out earlier, it is the DRM keys which isnt allowing the camera to activate, its not like the camera focus is passing wrong values, the camera doesnt function at all on focus, hw focus detector error, credmanager, looks like credmgr wants the keys but isnt receiving them so doesnt activate bravia/imageproccessor...
Methods to get this working would be...
1. Crack DRM (Difficult, I wont attempt this)
2. Kexec (delewer has been working on it and he has taken it far, in talks with him, attempting to help him whenever I can)
3. Run AOSP on stock kernel... (Anyone attempted this? Not sure... Can it be done? Most likely... (wont benefit from custom kernel e.g. Overclocking undervolting etc etc))
Best option looks to be number 2, kexec
Edit: Further testing, Lets see if I can fool the device in thinking I already have the keys...
Click to expand...
Click to collapse
Maybe we can plant a ta-dump on credmgr somehow? Maybe we can find the start-address where credmgr looks for TA, place the dump in ram und modify the address in the binary to point it there.
When the bootloader is unlocked, what is altered? Certain things stop working, like DRM content, I believe this is the main cause of the camera not working, I'm thinking is there a way to spoof the system, forcing it to believe that that specific part of the DRM (for the camera) is still intact, when the bootloader is unlocked? Perhaps if the app / program used to unlock the bootloader could be obtained and modified to allow the specific part of the unlocking to leave the camera intact ??? Just an idea.
Of course that would mean isolating it, which i can't see being easy.
Really bad on Sony's part for letting this happen, surely they would have tested it prior to releasing it ?
With that in mind it would seem that it was Sony's intention to have the camera not work if you unlocked the bootloader, really don't understand this approach.
Yes sony wanted to break camera, with all the stuff ive seen today contained within our devices... Breaking camera was no mistake by sony
4k wont happen unless Sony allow it, camera only passes 1080p, have to use specific yuv(Venus) format for 4k afaik, max fps available is 60 on both 720p & 1080p, no HFR(90. 120, 150fps mode available)
Will update OP with more information regarding what our cameras can support
Also i see the light at the end of the tunnel... Regarding kexec
Yeah, Kexec would be the workaround for that. The Keys would stay untouched cause of the old kernel and the new kernel will boot the system ... if the system then read the key, it will get correct values out of the partitions ... just in theory ...
So if we can get kexec to work, it may not break the camera and we have a good workaround for that ...
will try to help on kexec ... hopefully we can get it to work ...
---------- Post added at 11:37 AM ---------- Previous post was at 11:26 AM ----------
Desperanto86 said:
I did this many times and always cam worked fine. Just wipe cam data after restoring TA. And of course your TA must be backuped BEFORE first unlocking.
Click to expand...
Click to collapse
TA backup had been the first i have done so yeah, for sure BEFORE unlocking ...
haven't tried to wipe camdata so that was the fault ^^ ... will try it again
Just a thought... not sure if it is possible (since I'm not that familiar with embedded systems and such)..
but could it be possible that only certain parts of the TA-partition are restored when restoring the backup after unlocking, so the DRM-stuff is retained?
Guyz just want to know, camera will be back (from Sony or anothers) ??
kartal172 said:
Guyz just want to know, camera will be back (from Sony or anothers) ??
Click to expand...
Click to collapse
You really shouldn't be asking for this here. This issue is frustrating enough without having people asking for ETAs. If you want to help, pressure Sony online to give us an update on their status.
Sent from my K00C using XDA Premium HD app
cursordroid said:
You really shouldn't be asking for this here. This issue is frustrating enough without having people asking for ETAs. If you want to help, pressure Sony online to give us an update on their status.
Sent from my K00C using XDA Premium HD app
Click to expand...
Click to collapse
Just asking that is confirmed from Sony possible fix or any news?
kartal172 said:
Just asking that is confirmed from Sony possible fix or any news?
Click to expand...
Click to collapse
There is no confirmation. There is no news.
I have twitted them several times without answer
//I AM STILL TYPING AND WILL TAKE TIME << SO DONT REPLY
i had typed and mistakenly deleted the tab before clicking post :|...i will delete these two lines once i am done with everything//
guys!
something we are all familiar with on galaxy grand forum is spamming!
indeed there are still many users/new users who post WRONG POSTS in WRONG SECTIONS..
still u can find questions which are off-topic/not related to forum/which have been answered several times/which have been asked several times by making new threads etc.
it not only takes up unnecessary space on server, but also lowers the value of GALAXY GRAND DUOS community..
developers getting pissed by day to day ETA's and helpers pissed by posting same and same answer, to several people !
i do know that xda's search option on top right might be not that accurate for some here,
SO
here i am here making an illustrative thread,(after discussing and opinions from many on xda)
WHICH will not only help you to solve ur problems regarding roms, but also day to day frequently asked multiple times answered questions....
its possible that it does not contain everything that u need , but seriously guys, it will at least decrease number of SPAMS on our threads...
all problems will be mostly illustrated below.........
just read it once please before posting in all other forums....
Few Information better read before any Posting!! (most Important..)1. AOSP based Rom/ Non touchwiz Rom (cm11/carbon,resurection remix, paranoid android,Pac-man ,Omni,and others)DO NOT support DUAL SIM Functionality..(it Requires Broadcomm Specific Codes which are not released as Open Source)...
you want Dual Sim , be On any touchWiz based Rom(Stock, Gennxt , etc)..
2. Difference between Touchwiz based Roms and AOSP Based Roms of our Device
1. AOSP Roms DON'T HAVE Dual sim functionality.
2. these are small in size as have only basic android Framework and Do not include bloatwares.
(Roms size~198mbs+)
3. AOSP Roms don’t have TW features, (but have their own**)!
4. they are Highly Customizable and meant for performance.
5. Lower RAM Consumption compared to TouchWiz.
1. Touchwiz Roms HAVE dual sim functionality
2. TouchWiz Roms are Larger in size
because of heavy Framework and Bloatwares*
(ROM Size~844mb+)
3. Touchwiz Got its own specific Features and its own apps for Music/camera etc.
4.they got polish and looks (in own way).
5. High RAM consumption Compared to AOSP. * Custom Roms based on Touchwiz are mostly Bloats free.
**Features varies from Rom to Rom.....get a quicky info in Roms Section!
Recovery Mode and Download Mode
recovery mode- it is a mode used for multipurpose uses.......described below..
switch off the device..hold (vol. up +powe+menu) combination...and let device start..once device start...remove hands atleast from power button else it will switch it on again!!!
How to operate it???
use volume buttons to navigate up and down...
use power button to select!
stock recivery(by default samsung recovery has limited options below....
-reboot system now
(Reboots the system).
-apply sdcard:update.zip
(Install diverse updates like themes, custom roms etc.)
-wipe data/factory reset
(Deletes all the apps, data and system settings(Files on the external SD-card will stay untouched)
-wipe cache partition
(Only wipes (formats) /cache partition (sometimes used as temp storage for updates, market downloads, etc) it hasn't anything common with Dalvik-cache which is in /data by default and it implies that the following boot after wiping cache partition will not be any longer than usually.)
beacuse stock recovery is limited.....custom recoveries are important which have got special features like backup/restore...and many more..
I use CWM...and it is easy to use..i will tell in later section
Download mode- it is used to flash firmware by Odin...
Combination - (vol. down+menu+power button)
once it boots ..there will be a screen ..
volume up to confirm that u want to go ahead and flash by Odin.
volume down to backoff and restart if u did it by mistake.... using ODIN
(lifeline of Samsung firmware installers )
it is really simple app fpr windows PC to flash firmwares/kernels/recoveries etc.
when you brick your device, dont panic and post anywhere...just re-install the firmware by Odin for developer's sake
it will remove everything and simply will install the Samsung's firmware and will make your device like a fresh new one!
an app for saving asses of guys like me who unwillingly/unknowingly brick there device!!
Odin download
link~ http://bartztech.com/wp-content/uploads/YP-G1/Restore/Odin3v1.7.zip
Odin Prerequisites:-
When you need to flash using Odin, you need the Samsung drivers, so that Odin can detect your device while attached to PC via. USB cable....
- Samsung USB Drivers
linky~ http://www.mediafire.com/download/hzlnda0l5t8qyes/SAMSUNG_USB_Driver_for_Mobile_Phones(3).exe
download drivers
remove old ones installed by control panel(if any)
reboot
install the drivers given
reboot
ready to be used
A stock Samsung USB cable (it seems to give better result than other USB cable bought on third party sellers.)
Flashing by Odin
Note- An Odin flashable file is supposed to be in .tar or .tar.md5 format only.
1.Run Odin.
2. Put your device in download mode(switch off then press vol down+power+menu button altogether.....once it starts..leave buttons else will switch off again coz u are holding power button remember !!)
3.You should see a yellow/blue rectangle with COM:xx and saying ready. that is your device ID actually.. It means that your device is ready to be flashed! (It is important because it means that device connected is recognized by Odin )
4.Go into the PDA section and take your .tar file.(if single file is given.)
if multiple .tar files are given then put CSC in CSC...phone/modem in PHONE section respectively
5. if there is also a pit file then make sure that re-partition box at left is UNCHECKED>!!
6. meditate for a while and ensure once again hat files u have selected are for galaxy grand duos only !!
obvious if you flash s3 files by Odin..you will end up in boot loop..
7. hit start and pray to god that all goes well *kidding*..it will
8.When it's finished, it should say that it's done with a green box saying PASS..if it says fail.....i.e. your USB is not accurately detected...or is detected but disconnects in between.... it happens sometimes if it is not THAT GOOD usb cable...dont panic..remove battery and repeat all steps again!! .just dont let it touched even by air if that happens..keep trying and it will work...once work is done..the first thing u do is get a good USB cable (its i am talking about extreme cases , there will be no problem else )
once it is done , device will be rebooted ( if reboot is checked in left box(u will get what i am talking about once you open app and see by yourself)
Note:- if you have flashed a firmware..first boot might take time from 3-10 minutes...just keep patience and wait....
if still it doesnt start after 10 minutes ....remove battery...re-insert...go in recovery mode..clear data/format and clear cache..now reboot..wait again.... and you are good to go
ROOTING and CWM
basic reason why most of people come on XDA is how to root!
thanks to @chotu222 who already have made a thread so that people can follow and acquire what they wished!!
i will be short and still descriptive!!!
(as it is already mentioned in forums and its pain to type so much :/)
PROCEDURE:
simply for quick pickers.. install CWM and then flash superUser through it!!
is it really that difficult to do??
there is a cwm given with SeLinux support(which is must for installing kitkat roms ), so why not just install that CWM and be carefree (whatever u flash, it wont give any problem)
simple two steps.....
Step 1: installing CWM...
here is SeLinux supported CWM file..(thanks to @pawitp \m/ )
linky~ http://goo.im/devs/pawitp/i9082_cm11.0/recovery_20131210.tar
download it and flash via odin
NOTE- while flashing by Odin , untick auto reboot Option(because rebooting device makes stock recovery to over-write over CWM recovery....)
once the flashing process is done....simply remove and re-insert battery, and go to Recovery Mode, flash the Fix-Recovery.zip given below...
that will fix your problem
Fix-Recovery link- http://www.mediafire.com/download/74mmd1x4af6hlo4/Fix-Recovery.zip.
Step 2: installing superSU: SuperSU allows for advanced management of Superuser access rights for all the apps on your device that need root.
linky~ http://download.chainfire.eu/376/SuperSU/UPDATE-SuperSU-v1.89.zip
just flash the superSU by CWM.....
reboot the device...
and your device is now rooted(check it if there is a superSU app in ur app drawer or not).
that is it!!
that's all it takes to root your device...
just 5 minutes :/
NO..You wont loose any data..its just that you simply installed an app in system root directory
Custom roms
Custom Roms are customized Roms for devices..providing us with various different options/advantages over stock Rom what we have Pre-installed by company!..it could be a de-bloated same stock rom w or w/o extra features,/ a whole new version of android/ a ROM based with UI built for different mobile...
simply..there are many Roms and the list is actually long..i cant simply explain but still tried to....
They are mostly based on Aosp/Aokp format(in simple words, with look of nexus UI), or OEM's based(in simple words like Samsung's touch wiz, htc's sense)..
every rom has its unique specialty..unique UI and Unique features.
OEM's are heavily programmed and sized, bloated with factory apps pre-included..
that is the reason that nexus based Roms (~250Mbs+) are twice smaller than the official firmwares(~800Mbs+)!
thanks to all respected Developers who did put such their efforts, and have provided us with so many ROMs !
i am enlisting all ROMs down here with short descriptions, so that you can find everything under one thread here!
AOSP BASED ROMs-
Kitkat (android 4.4.2)
CyanogenMod 11-
thanks to @pawitp for developing this Rom. i dont think i need any explaination for CyanogenMod
its basic AOSP Rom based on Kitkat(4.4.2)...used as base rom for many Custom Roms, It is considered as standard Rom by many Users...Good battery backup,performance and less RAM consumption is speciality of this Rom..it don't implement much extra features except basics, as try to be as near to Nexus stock rom!
developer is always trying to update it as soon as CyanogenMod releases any update...
pawitp has also given delta update Option if you are using limited mbs and internet..its like update and patches which are directly supposed to be flashed (and are <20mbs)..just the modifications made are given , so that you dont download the whole rom...
NOTE- just read FAQ section in cm11 thread for more information on Delta updates.
thread link-http://forum.xda-developers.com/showthread.php?t=2563557
media Fire link for latest Update(thanks to @naufalhadyan)- http://www.mediafire.com/download/1toub3foiqaz9c4/cm-11-20140109-UNOFFICIAL-i9082.zip
Carbon Rom
One of the most appreciated Rom Built for galaxy Grand i9082 @xenon92 did put some serious green lantern efforts here (the reason why it has got amazing battery backup and performance)
personally, have used many Roms built for the device,but carbon Rom was the one with least problem when Run by ART compiler..
not only its RAM usage decreased from avg. 300 to 210, but also it supports Gapps in ART (while many Roms conflicts with gapps and give FCs in ART)
it has got many add-on features then just plain kitkat Roms...With the possibility of Halo getting Implemented it Near future(Depends on Carbon Team), lockscreen blur, notifications on lockscreen and Active display comprised as its one of good add on features, there is a Good battery backup (actually good,), with performance..
just give it a shot and u will love it
see rest of information on thread itself..
thread link- http://forum.xda-developers.com/showthread.php?t=2567881
direct download link for latest build(not a mirror but given in OP itself)-http://www.androidfilehost.com/?fid=23311191640114163
SlimKat
One of best thing about @xenon92 is that once he starts rolling new roms, he just cant stop ....
so again, introduced slimRom with kitkat power..
slimRoms are most light weight code based Roms , for performance!..they don't add any extra features(Halo and all) because performance is MUST
good when it comes to battery backup
just install and u will never regret it
more description in thread.....
thread link-http://forum.xda-developers.com/showthread.php?t=2567869
latest version direct download link(no mirror,just link to download)-http://www.androidfilehost.com/?fid=23269279319196481Resurrection Remix®
OmniRom
ProBam Rom
KitKat-X
Paranoid Android
I hope this will cause less spamming and also keep writing guides
Sent from my GT-I9082 using Tapatalk Pro
@raghavsharmaxda..bro in continuation to your post, i wud like to suggest that u may add a section on EFS backup also...that's pretty much vital...
skpadhi79 said:
@raghavsharmaxda..bro in continuation to your post, i wud like to suggest that u may add a section on EFS backup also...that's pretty much vital...
Click to expand...
Click to collapse
I am doing.. Pretty much is left..what i have is just 10 percent yet..
Kernels...all roms...descriptions..gapps...how to do xxxx or yyy functions.. How to solve basic problems...efs. Iceyhotguy's tweak...hyperlinking to faq thread of chotu222.....much more to be done :|.
Trying my best ..but it's not easy to collect all points from projects from last year till date...in just one day ...trying and will.....
Ps- just realising that indent header grouping dont look good at all in tapatalk :|..i domt know how @iceyhotguy did it..i have done and on pc its great...
Sent from my GT-I9082 using Tapatalk
@raghavsharmaxda........well !! Rome wasn't built in a day..............:good::good:
raghavsharmaxda said:
I am doing.. Pretty much is left..what i have is just 10 percent yet..
Kernels...all roms...descriptions..gapps...how to do xxxx or yyy functions.. How to solve basic problems...efs. Iceyhotguy's tweak...hyperlinking to faq thread of chotu222.....much more to be done :|.
Trying my best ..but it's not easy to collect all points from projects from last year till date...in just one day ...trying and will.....
Ps- just realising that indent header grouping dont look good at all in tapatalk :|..i domt know how @iceyhotguy did it..i have done and on pc its great...
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
Thanks dude!
Sent from my GT-I9082 using Tapatalk
@raghavsharmaxda I've uploaded the newest CM11 update (200140121) to Mediafire, please update the mirror link above. Here is the link
naufalhadyan said:
@raghavsharmaxda I've uploaded the newest CM11 update (200140121) to Mediafire, please update the mirror link above. Here is the link
Click to expand...
Click to collapse
Updating right away..
I almost forgot to complete this thread due to some reasons...by today i ll do whole../most of..
Sent from my GT-I9082 using Tapatalk
Posting in the wrong section
@raghavsharmaxda you are posting in the wrong section!!!!
Post this in the general section.
The main reason I postes this here is coz many do come here for FAQ thread..
So its better that they read it here near FAQ thread (so that ppl think twice before posting noon kinda qsns in FAQ too and helpers do save sometime !!).
Still if its a trouble I will surely move it..
Thanks for advice...
Sent from my GT-I9082 using Tapatalk
+1...i also somehow feels the same......with grand becoming older and older down the line.......there wud be probably more activities in Q & A section with no more stock firmware upgrade and amazing devs developing new roms ( hopefully ) and new probs wud arise if any......
it's great someone has decided to write down all the important things we need to know of our phones in one place... Thanks a lot @raghavsharmaxda :d
Sent from my GT-I9082 using Tapatalk
shanbhagatul said:
it's great someone has decided to write down all the important things we need to know of our phones in one place... Thanks a lot @raghavsharmaxda :d
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
Glad u liked it...but i am still updating..and my pc is gone for fixing..:-|..
And tapatalk is not editing...thats why i m making this late here.. Sorry everyone for trouble
Sent from my GT-I9082 using Tapatalk
raghavsharmaxda said:
Glad u liked it...but i am still updating..and my pc is gone for fixing..:-|..
And tapatalk is not editing...thats why i m making this late here.. Sorry everyone for trouble
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
hey @raghavsharmaxda i had a small request...could you include explanation to various features in the roms in this thread of yours? there are some features which i have no clue what they do and what they are meant to do...so if possible ...thanks anyways
raghavsharmaxda said:
Glad u liked it...but i am still updating..and my pc is gone for fixing..:-|..
And tapatalk is not editing...thats why i m making this late here.. Sorry everyone for trouble
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
Please also tell about AOSP doesnt has dual sim right now, to stop spam about dual sim.
No rude...
Sent from my GT-I9082 using Tapatalk
black87 said:
Please also tell about AOSP doesnt has dual sim right now, to stop spam about dual sim.
No rude...
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
How cud it be rude ..its too obvious as is pain all the time..yea..i will make a big list at top about few things ppl do.....
Sent from my GT-I9082 using Tapatalk
raghavsharmaxda said:
How cud it be rude ..its too obvious as is pain all the time..yea..i will make a big list at top about few things ppl do.....
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
I also suggest adding site-specific Google search, it's a lot better than XDA search. It should help a lot of newbs.
Add "site:xda-developers.com" after the keywords i.e. "battery drain problem site:xda-developers.com" and type it into Google search. It also works on other sites, not just XDA.
naufalhadyan said:
I also suggest adding site-specific Google search, it's a lot better than XDA search. It should help a lot of newbs.
Add "site:xda-developers.com" after the keywords i.e. "battery drain problem site:xda-developers.com" and type it into Google search. It also works on other sites, not just XDA.
Click to expand...
Click to collapse
Aye aye captain
Ur suggestions are always welcome ..
Sent from my GT-I9082 using Tapatalk
i have installed cm11 on my grand, and i want to install stock firmware but when i am connecting it odin does'nt show a blue/yellow box com:xx.....
i have tried changing ports and cables and also restarting the apps but still not working and earlier when i had stock frimware it detected without any issues.....
what could be reason?
ssach30 said:
i have installed cm11 on my grand, and i want to install stock firmware but when i am connecting it odin does'nt show a blue/yellow box com:xx.....
what could be reason?
Click to expand...
Click to collapse
Did you go into download mode? what version of odin did you use? use 3.04. Try to change usb cable. tell me if no one of this working.
All THESE TOOLS ARE MADE BY ME FOR THE PURPOSE OF FIXING FREEZED SCREEN AND NOT WORKING CAMERA ISSUE BUT NOT SERVING ANYONE HERE. USE IT OR NOT, IT"S YOUR CHOICE.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in these TOOLs
* before using them! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
=====================
= FREEZED SCREEN ISSUE =
=====================WARNING
Do not use Automatic Tool more than once for each kernel (boot image).
If you did that by accident and device can not boot. Just reflash original kernel then use the tool again.
HOW TO UNLOCK BOOTLOADER WITHOUT FREEZED SCREEN?
- Unlock Bootloader Tool (2 recommended options: 1-1-5 or 1-5-5)
- Root your device.
- Enable USB Debugging.
- Extract and run this tool (Download) - READ INSTRUCTION WHEN TOOL IS RUNNING.
- From your device, using any File Explorer to copy cmdline file from /sdcard to /d/osip
- Reboot device.
CHECK IF TWEAK IS APPLIED OR NOT
- Use any File Explorer to get into root folder
- Check if value in /proc/cmdline has "... intel_idle.max_cstate ..."
READ THIS OR I WILL NOT CARE WHATEVER YOU COMMENT HERE
- Who used my tool and get thing fixed, help the others if you can.
- If you tried all options of unlocking bootloader and applied tweak but your devices still get freezed and automaticly reboot, get last_kmsg by using Kernel Auditor (right after reboot) then post in the comment section.
- Just like above but if it's freezed without reboot then I'm sorry that I can't do anything for now.
OPTIONAL
- TWRP-3.0-B-5.0 flashable zip with tweak applied. Freezing is not occured much on TWRP but I still make this one for personal and for people wanna get rid of freezing when flashing something in TWRP. (Download)
Thanks to @X AnwarMov
- TWRP-3.1.1-0 fastboot image with tweak applied. (Download)
Thanks to @narueon
WORK UPDATE (05/09/2017)
05/09/2017
- Re-enable kernel watchdog
15/07/2017
- Tool now can be used in any rom.
09/07/2017
- Fix cmdline code.
- Remove init.d file since all issues are fixed by cmdline.
08/07/2017
- Remove "processor.max_cstate" parameter for battery issue
07/07/2017
- Just finished some works and tests
05/07/2017
- Add more boot options to cmdline.
- Try to complete the tool.
- Add 3.87 kernel for stock users.
- Out of data, may be no more update for while
04/07/2017
- Remove "disable_kernel_watchdog" parameter to kernel cmdlines.
- Add "acpi=off" boot option.
- Disable thermal charging limit.
30/06/2017
- Start testing in public
=========================
= CAMERA NOT FOUND ISSUE =
=========================NOT FIXED YET
For anyone is facing this issue, I will keep asking for stuff here when I have any idea
Stay tuned for any update in this post
And also remember, I don't have device with this issue for test so don't ask why it takes so long to fix.
REQUEST
Get 2 different dmesg files then send me via private message or telegram.
- One right after boot
- And another after open any camera app
You can take dmesg file by using Lspeed, Kernel Auditor or any method that you've already known
TROUBLESHOOT
1. Module Problem
HM2056 module can not be used. This is one of camera modules.
Credits
@nheolinkin
@juyel92
@X AnwarMov
@narueon
And all testers.
MODIFYING THESE TOOLS IS DENIED / REDISTRIBUTING MY TOOLS AT OTHER FILE HOSTING SERVICES IS DENIED / REPOSTING THESE TOOLS AT OTHER WEBSITES WITHOUT PROPER CREDITS, BLOATED WITH ADS OR WITH DOWNLOAD PROTECTION/REGISTER-TO-DOWNLOAD IS DENIED / IF YOU IGNORE IT, I WILL ASK MODERATOR TO DELETE YOUR THREAD OR I WILL DO A FORMAL DMCA TAKEDOWN.
================
= INFORMATIONS =
================
[TOOL] Fix Freezed Screen/Camera Issue With Unlocked Bootloader for Zenfone 5
Contributors
@nheolinkin
Status: In Progress
Last updated: 2017/09/05
RESERVE
Wow, Thanks im really happy after reading this stuff, it helps me to understand why freezing happens and how fix part of this problem, you have my "thanks" anyway i have question, why unlock doesnt couse any problems on kitkat based firmware?
kihope12 said:
Wow, Thanks im really happy after reading this stuff, it helps me to understand why freezing happens and how fix part of this problem, you have my "thanks" anyway i have question, why unlock doesnt couse any problems on kitkat based firmware?
Click to expand...
Click to collapse
You mean "unlock" by unofficial tool or asus's app? If it's unofficial tool does not cause any problem in kitkat base but not lollipop then I need to talk to that "guy"
nheolinkin said:
You mean "unlock" by unofficial tool or asus's app? If it's unofficial tool does not cause any problem in kitkat base but not lollipop then I need to talk to that "guy"
Click to expand...
Click to collapse
Im sure for 99% unofficial unlock doesnt couse freezing on 4.4, i used official only one time, but unofficial is just flashing ifwi and dnx from officiall firmware.
kihope12 said:
Im sure for 99% unofficial unlock doesnt couse freezing on 4.4, i used official only one time, but unofficial is just flashing ifwi and dnx from officiall firmware.
Click to expand...
Click to collapse
The fact is that if unofficial unlock doesn't cause freezing on 4.4 then it won't cause freezing on any base.
And the official one, pretty the same except that it can detect your unsupported devices if you're using later kitkat rom.
For example, If anyone buy a new device with 2.20.40.13 manufactured rom, official tool will tell you exactly that your device is supported or not. But if you downgrade to any rom earlier than that then it won't, because it just simply can not realize your new device with new mainboard and stuff inside.
nheolinkin said:
The fact is that if unofficial unlock doesn't cause freezing on 4.4 then it won't cause freezing on any base.
And the official one, pretty the same except that it can detect your unsupported devices if you're using later kitkat rom.
For example, If anyone buy a new device with 2.20.40.13 manufactured rom, official tool will tell you exactly that your device is supported or not. But if you downgrade to any rom earlier than that then it won't, because it just simply can not realize your new device with new mainboard and stuff inside.
Click to expand...
Click to collapse
But why on 4.4 it doesnt freez, and on 5.0 up it does?
kihope12 said:
But why on 4.4 it doesnt freez, and on 5.0 up it does?
Click to expand...
Click to collapse
Which tool did you use? How long do you use kitkat to ensure that it won't freeze?
nheolinkin said:
Which tool did you use? How long do you use kitkat to ensure that it won't freeze?
Click to expand...
Click to collapse
I used both, official at first time then I used unofficial beacuse official doesnt works at .44, kitkat i use very long timw ago. Or only for while when i reflashing whole system.
kihope12 said:
I used both, official at first time then I used unofficial beacuse official doesnt works at .44, kitkat i use very long timw ago. Or only for while when i reflashing whole system.
Click to expand...
Click to collapse
My bad then, I forgot to mention fastboot of later base than 2.21.40.44 does not allow flasing ifwi so official tool's not supposed to work proberly.
And about your case that it's just freezed in 5.0 instead of kitkat, it's hard to say but it could be caused of 2 reason:
- not compatitive bootloader (dnx) version. Because after all if.bin file and also official tool are made for kitkat but not lollipop.
- if frequency of freezing is low, then it could be something else that I can not say for sure without logs.
Conclusion: Can unlock bootloader or not, it's based on the result we got from kitkat rom. That's why I do not mention 5.0 here.
thanks to you im so happy u made this thread..
anyway i had some question...
we know that disabling 2 cpu core will fix this freeze issue..but with a cost of performance and broken camera
and... "sometimes" if i play a game especially the heavy one,ex:vainglory... the freeze is gone
i wobder why that things can prevent the phone to freeze??
nheolinkin said:
My bad then, I forgot to mention fastboot of later base than 2.21.40.44 does not allow flasing ifwi so official tool's not supposed to work proberly.
And about your case that it's just freezed in 5.0 instead of kitkat, it's hard to say but it could be caused of 2 reason:
- not compatitive bootloader (dnx) version. Because after all if.bin file and also official tool are made for kitkat but not lollipop.
- if frequency of freezing is low, then it could be something else that I can not say for sure without logs.
Conclusion: Can unlock bootloader or not, it's based on the result we got from kitkat rom. That's why I do not mention 5.0 here.
Click to expand...
Click to collapse
I think it is first problem what you mentioned, anyway why asus didnt make if.bin for 5.0 it is impossiblle or it is beacuse they are lazy as moct of time?
andyfahri7 said:
thanks to you im so happy u made this thread..
anyway i had some question...
we know that disabling 2 cpu core will fix this freeze issue..but with a cost of performance and broken camera
and... "sometimes" if i play a game especially the heavy one,ex:vainglory... the freeze is gone
i wobder why that things can prevent the phone to freeze??
Click to expand...
Click to collapse
Disable 2 cores won't fix freeze issue but just decrease frequency of it. You don't need to throw away performance and camera for that.
And yes, some game will not cause freeze when you play. If I'm not wrong, how your figure touch the screen in game could be the reason. For clearly, it won't be freezed or least freeze when you play a game that one or more than one figure touch the screen continuously when playing.
VainGlory is an Moba game which is perhaps required 1 figure touching continously to move characters right?
kihope12 said:
I think it is first problem what you mentioned, anyway why asus didnt make if.bin for 5.0 it is impossiblle or it is beacuse they are lazy as moct of time?
Click to expand...
Click to collapse
They are not paid for doing that
nheolinkin said:
Disable 2 cores won't fix freeze issue but just decrease frequency of it. You don't need to throw away performance and camera for that.
And yes, some game will not cause freeze when you play. If I'm not wrong, how your figure touch the screen in game could be the reason. For clearly, it won't be freezed or least freeze when you play a game that one or more than one figure touch the screen continuously when playing.
VainGlory is an Moba game which is perhaps required 1 figure touching continously to move characters right?
Click to expand...
Click to collapse
yepp... ur right sir,now i understand why freeze happens more often on menus than when playing the match
andyfahri7 said:
yepp... ur right sir,now i understand why freeze happens more often on menus than when playing the match
Click to expand...
Click to collapse
my phone doesnt freez when i play games but it freez a lot when i watching youtube and doesnt touch touchscreen while..
AUTOMATIC TOOL WAS RELEASED
Take a look at the 2nd post for detail
nheolinkin said:
AUTOMATIC TOOL WAS RELEASED
Take a look at the 2nd post for detail
Click to expand...
Click to collapse
Hello there , saw about kernel panic . I too experience sometime reboot due to kernel panic . Then i disable kernel panic and everything is fine for me. You got any idea to fix ? And i am totally confident its bug in kernel not in bootloader
Boomshiva said:
Hello there , saw about kernel panic . I too experience sometime reboot due to kernel panic . Then i disable kernel panic and everything is fine for me. You got any idea to fix ? And i am totally confident its bug in kernel not in bootloader
Click to expand...
Click to collapse
It depends on last_kmsg you get after panic. There are quite a lot reason for kernel panic that I can not say for sure.
nheolinkin said:
AUTOMATIC TOOL WAS RELEASED
Take a look at the 2nd post for detail
Click to expand...
Click to collapse
What about kernels for 6.0 and 7.1.x cm and aosp based?
I have been out of the loop for 3 years, since last flash. I did a half root thing where certain camera modules weren't touched, is this still a thing? Also I have no clue what this purple notteamwin is
What rom would you recommend me for best physical button snapshot machine?
thx
Edit, I run this odd traffic series blog 1picaday. berlinwaiting.tumblr.com Today nopic due to bootloop, tomorrow maybe a new shiny rom and continuity, pls xda I need guidance
qx876 said:
I have been out of the loop for 3 years, since last flash. I did a half root thing where certain camera modules weren't touched, is this still a thing? Also I have no clue what this purple notteamwin is
What rom would you recommend me for best physical button snapshot machine?
thx
Edit, I run this odd traffic series blog 1picaday. berlinwaiting.tumblr.com Today nopic due to bootloop, tomorrow maybe a new shiny rom and continuity, pls xda I need guidance
Click to expand...
Click to collapse
Maybe this is not what you are looking for, but this sounds as great ROM
https://forum.xda-developers.com/sony-xperia-z1-compact/development/rom-t3657384
( I didnt test, just reading the thread )
the rom JIJOK mentioned, is very good. I am using it atm. But "half root" and "noteamwin"... I think you should read the threads very carefully. At first get real recovery (Sony EMMA Tool) and TWRP (yes team win).