Related
I am new to this, but i have been working on unix based OS for years
I was wondering the other day i updated too this new update from oxygen, and i noticed my settings for data over the sim card keeps reseting too what i had before update. I force the phone too use only 2G networking, I now have too reset it each and everytime I reboot, the phone. It also seems like there is a few other apps that dont keep their settings.
Its most certain a file permission setting that is wrong, but since i have not been using this before. I was hopeing too get a few pointers of what files that might have broken permission?
Anyone that knows what i am looking for?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
So i am here with a new idea. A rescue.zip which can be used to rescue any android device which have a recovery like the famous cwm.
So here is it..
Some times we people screw up our android os like hell, and to reboot the device we usualy do a recovery flash of a new os, flash back our nandroid backup ( both on worst conditions) or even do permission fix, clean cache or dalvic cache( those in 'not that worse' conditions) . So thats are all the options we got. Rit?
Although flashing recovery backups, new roms can fix all, it will also eatup our apps, current setups, contacts, msgs, etc( in case we dont have backups) and will probably screw us. All we can do is say " WTF..WTF..WTF.."
SO here is my idea,
Find out the causes of what causes a reboot, non-boot, hang,fc etc.
And keep a zip that can be flashed through recovery, that has a solution for our problem. They may be including..
1) fix permission of system, data, and user data.
2) zipalign the apps
3) fix the default clock speed of processor
4) defragment memory
5) flash a new copy of su and busy box
6)wipe data or system or ext or cache or dalvic cache
7) flash a new copy of framework.res, system-ui.apk, settings.apk with default permissions( those files are kept in separate "custom" folder on the zip, so that end user can put their own files to that "custom" folder for flashing., the reason behind it is known to all, yap. Not all devices have them in common, every device have its own files)
These are all i got for now, pls post ur ideas and knowledge for any possible cure about any problem u faced/ cured. So that we can make it an ultimate rescue.zip that have a cure for 99% problems android os have. The rest 1% will go with a clean flash.( well we cant avoid that if we did something that bad).
So my plan is to use aroma installer( now on hard learning to find how it works). Throw in some scripts, files etc. Into the zip.
And since its not a device specific .zip file, i want to know how and why any problems are caused in any device( there are many common problems, but that is not what i ask for. I ask for device/os specific problems, and not for a problem that we can cure after booting, but for a problem that can make the device un-bootable) . So u people may help me to find those problems and cures for it. For my knowledge i have experience with wildfire and hd2.
Well i will keep this thread for a week or two, so that u can post ur knowledge, and info. after that i will release the file for u.
To the admin. Of the forum, pls keep this thread as announcement so that all can take a look.
HYPERDROID EXTREEM EDITION-THE NEW BENCHMARK ROM FOR HD2.
I like Aroma, thanks for pointing that out! And yes... good idea... and a lot of work
Sorry but this is not development but merely an idea.
As soon as you have something that can be downloaded or something that shows active development (Git, sources, progress reports, individual scripts) then you can pm me to reopen the thread.
PS: You can also open such a thread in the general subforum.
Hey guys.
Due to the thread closing by OP's instructions on http://forum.xda-developers.com/showthread.php?t=2422404, I've decided to continue the discussion on this thread as everyone else who was getting help on there (including myself) now can't because of that.
The idea is to help each other as the original thread's intentions were, regardless of our expertise and knowledge, because it is well-known that every small contribution can be helpful for a device or another, with enough knowledge
Just like the original thread, post your problems and solutions related to the MT6577 chipset, including porting from MT6589/MT6573/etc. devices. Politely and nicely, please.
I will start with a question I've had for a few days: Does anyone know what are the binaries and files which control the battery metering/values? In my port, I'm having a problem where a reboot takes around 20% battery, and even if the phone is with 1% remaining, it can last as much as if it has 20% remaining or something. Mine is a port of the Lenovo 4.2.2 ROM.
Any ideas?
As an note i closed it due to spamm.
(and The thread was cleaned at least 2 times)
For an base port, the info is all there.
Also The tools for port i.e.: to patch kernel ramdisk, its here on xda, an simple search will point you to that. Or you can simple use The Kitchen to extract your zlimage and replace the one in my boot.IMG as my ramdisk is already patched for 4.2.2 , and thats The one i used to patch everyones boot.img when someone requested me.
Also theres already an 2nd thread about MT6577 porting to 4.2.2
And there are fixs that are device dependent, people must understand that, and it will require work and debugging from their side!
As i said this is for advance users only, if people cant work with something simple as ADB, they shouldnt try this port.
Regarding your question, thats an known old Android bug.
The battery Stats frozing. Usually wiping cache and Dalvik fixs it for some time.
And after an ROM change you should always recalibrate your battery.
B.regards
superdragonpt said:
As an note i closed it due to spamm.
(and The thread was cleaned at least 2 times)
For an base port, the info is all there.
Also The tools for port i.e.: to patch kernel ramdisk, its here on xda, an simple search will point you to that. Or you can simple use The Kitchen to extract your zlimage and replace the one in my boot.IMG as my ramdisk is already patched for 4.2.2 , and thats The one i used to patch everyones boot.img when someone requested me.
Also theres already an 2nd thread about MT6577 porting to 4.2.2
And there are fixs that are device dependent, people must understand that, and it will require work and debugging from their side!
As i said this is for advance users only, if people cant work with something simple as ADB, they shouldnt try this port.
Regarding your question, thats an known old Android bug.
The battery Stats frozing. Usually wiping cache and Dalvik fixs it for some time.
And after an ROM change you should always recalibrate your battery.
B.regards
Click to expand...
Click to collapse
Hey man
Oh, thanks for answering on here, that was quick hehe thanks for the extra info!, I'll be sure to add it to the OP in a bit .
By the way, where is that 2nd thread? I know there is one about a tool by yuweng but it was more generic (for MT65xx and any version porting), is that the one you're refeering to?
Alright, well, I've never suffered from the battery bug until I started experimenting with this Lenovo ROM so something tells me there must be something different to it. I've used your ROMs (both 4.1 and 4.2) and never had that issue, so I'm suspecting it must be something with the ROM itself. Do you happen to know which files or binaries hold some code for the battery? I want to experiment, but with so much files around (i2c, bmt, etc) it's hard to get a starting point
About the battery stats, where are those stats located? My TWRP 2.5.0.0 doesn't have any "wipe battery stats" function and some battery stats apps I've tested can't find the stats file. Did they move it in JB 4.2 or something?
Again, thanks a lot for your advice
Thats normal, twrp and The latest CWM ( you can also try The latest up to date cwm for our ZTE, The carliv touch) that i ported, it also doesnt have that option, it was removed from The cwm source, since thats actually useless. The only thing it does is deleting one file located at /data/system/batterystats.bin this file is used ONLY for The Android battery statistics, nothing else.
If you are experience that bug more times on another ROM (port) its an indicator that some files on The ROM, are not indicated for your phone (usually its The /system/bin) files. just replaced those with your stock ones.
The thread i mention, its not that one, i will post it here later, im on The phone, so i cant use The search...
B.regards
im always stuck in bootlogo, never see the homescreen.
data connection not working
when i toggle data connection it turns on but no
icon on top
example : E , G , 3G etc
3g is not supported in my area
So I accidentaly removed the odex file for Google Service Framework,after a lot of tries to fix it I got into recovery mode and wiped the data from there...now I can't get past the introduction screens(the google services,name introduction and date & time setting tabs reapear over and over again)...and the error"com.google.process.gapps" has stopped working appears over and over again...so does anybody know what should I do?
I see you posted a long time ago, i hope you fixed the problem? If not, I'll be making a post in a few days, uploaded all the files on Mediafire tonight. Just to reach 10 posts for links. I actually did it. I think it has to work on every LGX150. I've found working ROM, and all other tools necessary. The only requirement is for you phone to be able to be recoginzed in device manager.
Also, I'll link other users I've seen are facing similar issues:
@s7L, @PaddiM8,
@spielwuffi Does your PC actually make any sound? Can any device be seen in Device manager?
1.Okay so, in this thread I'm going to post a fix for the infamous mobile data bug I.e mobile data which stubbornly refuses to turn on until restart
2. Substratum weird notification toasts after installing dark themes in which the lowercase y,g,q are incompletely rendered or else, in simple terms, they look weird because the lines don't seem to fit the toast
3. Only 2g bug
3. Overheating bug and battery drain
4. People who are sceptical about doze
5. No sim detected problem
6.Video recording bug
7. And if any more bugs, please mention. The above ones are all fixable although 5th and 1st require some workaround.
Important note. : to make sure that you don't encounter any sim card problem, clean flash this ROM only if you have flashed the official ROMs
Fixes :
1. Install any cm13 nightly. Dial *#*#4636#*#* and change the network type to WCDMA(3G) Preferred (or any G according to your choice). I recommend this step as a must because it hardwires the device to use all of types of desired networks and not enforce only 2g. Also, *please note to insert the data sim in the first slot only* in order to properly use this functionality.
If you are done with the above step, congrats, 80% of the work is already done. Open root explorer and go to /system/etc/apnconfig.XML (something related to APN and I'm sure it'll be the first file). Copy the file and save it somewhere in the internal or external memory.
Now flash android 7.0 and replace the same file in /system/etc/ and set the permission to read only I.e disable every right to write that file.
(This will work in most cases. If not then its a modem issue perhaps )
Edit : I found a new fix. Change the APN name to EE
and APN to everywhere
2. Go to display, change the display size to large and text size to small.
3. Flash the latest ROM of AOSP and disable clusterplug. There's already a tutorial on it in moto x play section. Please google it also govtuner is reportedly working.
4.doze works and phone goes to deep sleep. Observed via EX kernel manager
5.flash the stock ROM properly and then reflash this. Also possibly this is due to .70 volte update. So make sure you use the .52 update before flashing this ROM
6.use google camera and set the quality to 720p
7.you mention.
I'm no developer and I love to experiment. I'll make it a point to experiment on any other bugs if present
Thank you and please post your opinions.
Update : I disabled the aggressive doze in greenify and the data seems to work with the normal apn settings 'apparently'. Although this is the case with android n only. I didn't face this whole using cm13
Also I recommend periodic clearing of partition cache
This is definitely posted in the wrong section. What about this thread implies "Original Android Development" ?
Should be in the general discussion section.
Men thks for the post but, can you xplain how can i do the cluster plug off ? can you help me please
FanDroid09 said:
This is definitely posted in the wrong section. What about this thread implies "Original Android Development" ?
Should be in the general discussion section.
Click to expand...
Click to collapse
The whole point was, the ROM was included in this section. So people will automatically see this post if they are facing any problems. Please understand the logic behind this
anderson.laverde said:
Men thks for the post but, can you xplain how can i do the cluster plug off ? can you help me please
Click to expand...
Click to collapse
http://forum.xda-developers.com/mot...r-plug-enable-disable-stock-cm-t3422345/page4
kpamkar said:
The whole point was, the ROM was included in this section. So people will automatically see this post if they are facing any problems. Please understand the logic behind this
Click to expand...
Click to collapse
Still the wrong section
Why is this needed? Most workarounds are told already. And this should be in general not development
kpamkar said:
The whole point was, the ROM was included in this section. So people will automatically see this post if they are facing any problems. Please understand the logic behind this
Click to expand...
Click to collapse
It doesn't matter what your logic is. This section is for developers that are posting their original work.
The point is to keep the forums properly organized. Not to make it as easy as possible for users who can't search a thread for solutions that have already been talked about.
kpamkar said:
1.Okay so, in this thread I'm going to post a fix for the infamous mobile data bug I.e mobile data which stubbornly refuses to turn on until restart
2. Substratum weird notification toasts after installing dark themes in which the lowercase y,g,q are incompletely rendered or else, in simple terms, they look weird because the lines don't seem to fit the toast
3. Only 2g bug
3. Overheating bug and battery drain
4. People who are sceptical about doze
5. No sim detected problem
6.Video recording bug
7. And if any more bugs, please mention. The above ones are all fixable although 5th and 1st require some workaround.
Important note. : to make sure that you don't encounter any sim card problem, clean flash this ROM only if you have flashed the official ROMs
Fixes :
1. Install any cm13 nightly. Dial *#*#4636#*#* and change the network type to WCDMA(3G) Preferred (or any G according to your choice). I recommend this step as a must because it hardwires the device to use all of types of desired networks and not enforce only 2g. Also, *please note to insert the data sim in the first slot only* in order to properly use this functionality.
If you are done with the above step, congrats, 80% of the work is already done. Open root explorer and go to /system/etc/apnconfig.XML (something related to APN and I'm sure it'll be the first file). Copy the file and save it somewhere in the internal or external memory.
Now flash android 7.0 and replace the same file in /system/etc/ and set the permission to read only I.e disable every right to write that file.
(This will work in most cases. If not then its a modem issue perhaps )
2. Go to display, change the display size to large and text size to small.
3. Flash the latest ROM of AOSP and disable clusterplug. There's already a tutorial on it in moto x play section. Please google it also govtuner is reportedly working.
4.doze works and phone goes to deep sleep. Observed via EX kernel manager
5.flash the stock ROM properly and then reflash this. Also possibly this is due to .70 volte update. So make sure you use the .52 update before flashing this ROM
6.use google camera and set the quality to 720p
7.you mention.
I'm no developer and I love to experiment. I'll make it a point to experiment on any other bugs if present
Thank you and please post your opinions.
Click to expand...
Click to collapse
Moved out of the Development sections to here....
can you give the important parameters from: /etc/apnconfig.XML
thnx
New fix is mentioned. Please check
E:Unknown Command[log]
E:Unknown Command[log]
Error when flashing any nougat rom
PSxplay said:
E:Unknown Command[log]
E:Unknown Command[log]
Error when flashing any nougat rom
Click to expand...
Click to collapse
Not an error. Happens with everyone. Don't worry
I'm trying to go with RR5.7.4 / CM13 but AOSP / AICP N7.0.0. Returning to .52, install the kernel from axxx007xxxz / only for N, full wipe, wipe data. Does not help. "Insert SIM". When flashing an error in a previous post.
Rive188 said:
I'm trying to go with RR5.7.4 / CM13 but AOSP / AICP N7.0.0. Returning to .52, install the kernel from axxx007xxxz / only for N, full wipe, wipe data. Does not help. "Insert SIM". When flashing an error in a previous post.
Click to expand...
Click to collapse
Wait. Why are you flashing a different kernel other than what was given in the rom already ? Also you need to do a full flash which includes flashing of every single file in the retasia/reteu package
I need to go back through the fastboot on the stock?
Rive188 said:
I need to go back through the fastboot on the stock?
Click to expand...
Click to collapse
I guess so. It seems you messed up with the kernel settings. And please give me the exact details of the files you flashed
kpamkar said:
I guess so. It seems you messed up with the kernel settings. And please give me the exact details of the files you flashed
Click to expand...
Click to collapse
All files are taking on XDA. Now it sets RR 5.7.4. I tried to install AICP, AOSP.
Rive188 said:
All files are taking on XDA. Now it sets RR 5.7.4. I tried to install AICP, AOSP.
Click to expand...
Click to collapse
I'm sorry I didn't get you. Can you elaborate properly?