[Q] System not stabile + Sound output wrong, Help Me - Moto G4 Plus Questions & Answers

Hello,
i still did not find any direct solution for sound output dilemma, but i think i found a less elegant way by downloading an sound-output/input App, i dont know the english word exactly.
therefore the system (.... I guess in the Kernel? or in the Stock Android? or something like this... ) has wrong settings.
I had to switch output to speaker permantly, works ok for most of the time.
And the problem described is just a symptom, whether it is zdroid or lingeage, does not matter!
system ist not stabil! Sometimes it is, and then the apps close by thereself or system is rebooting without any reason or apps freeze etc. pp. ...
I do have just 8-15 apps, you know. You can exclude all those things you can search here or through google easily, i did this for a week, ok.
So i just needed a os which is very stable and very easy (performance first) and an hint from you all regarding the main cause (see above)?
For example i followed the advice of an user here, by installing stock android, i did, works, and the gapps/flashing os bei twrp (new version). done done...
what is the f** problem? I am so frustrated ,because i did these procedere maybe 6 times with other data / os(roms), you know?
So i need clear information about this cause.
And beyond that the device id is n/a or unknown if i boot my system. This device is not blabla... You know this screen?
(Problem Lineage + zdroid, does not matter) ...
Also the warnings ( i think google trust) <--- registering Google ID works through google.de website, but did not solve it (+ freezing system --> i flashed the best stable versions out there!!!)
Can you advice me, thanks Sir

Related

HELP ! ROM Update to Android 2.0 / 2.1

Hey Guys at first sorry for my english i'm not good in it. And I'm a Android newbie I just gained a bit exerience with my Touch Diamond but it's broken now..okay but that's not the probleme....
If got a question:
After about 2 days of searching for an android 2.0 or 2.1 ROM I was a little bit confused of the diffrent news everybody was talking about. I'm root on my Hero. That was the first an last thing I made with my device.
1. Everybody is gonna talk about MoDaCo 3.0 but when I was trying to download his ROM my browser never got a request. Is the site down, where that ROM is hosted ?? Could someone give me a working link with this ROM ??
2. Is there a ROM with Android 2.0 or 2.1 outside or even not ??? And if yes are they working well ???
Would be nice if someone can help me =) thanks a lot.
Please answer soon if you know something about that =)
Greetz BassdoxXx
you can get modaco's roms at his website, www.modaco.com.
in the android development section there are some 2.0/1 roms, none of them works flawless, see for yourself if it fits your needs.
Thanks a lot for your fast answer. =)
The problem that i couldn't open the modaco page was my isp -.- i downloaded it at school
BassdoxXx said:
Thanks a lot for your fast answer. =)
The problem that i couldn't open the modaco page was my isp -.- i downloaded it at school
Click to expand...
Click to collapse
What? Does ISP's block that site? Lol, would never happened in Norway
there is a few 2.0+ roms out there for the hero.
most seem to be very usable now.
best sense ui would be lox/behnaam community release on 1.6.
http://htcpedia.com/forum/showthread.php?t=1448
there are two aosp roms worth looking at.
lox aosp ( im using that on a daily basis)
http://htcpedia.com/forum/showthread.php?t=1416
jnwhiteh aosp
http://htcpedia.com/forum/showthread.php?t=1528
Hello all,
I am having very specific request when it comes to choosing a proper rom for install on to my hero.
I am blind. Stock roms are only running Android 1.5. More robust accessibility features are available starting with Android 1.6 and improving even more with Android 2.0.
So for sure I am forced to upgrade my hand set.
There are various roms, some of their authors have even disable google specific features so I know I can't install such a rom.
All the accessibility efforts are being lead by the google developers.
Most likely these accessibility tools won't be usefull to most of you but please can anyone recommend me a rom where market is working and where the following applications can be installed and used?
- eyesfree suite of applications,
- talkback - the google screen reader for android,
- tts service.
All possible help is already appreciated.
sorry for the double posting. I've accidentally posted twice and I am unable to remove the post.
Hope anybody can help me please.
pvdeejay said:
Hello all,
I am having very specific request when it comes to choosing a proper rom for install on to my hero.
I am blind. Stock roms are only running Android 1.5. More robust accessibility features are available starting with Android 1.6 and improving even more with Android 2.0.
So for sure I am forced to upgrade my hand set.
There are various roms, some of their authors have even disable google specific features so I know I can't install such a rom.
All the accessibility efforts are being lead by the google developers.
Most likely these accessibility tools won't be usefull to most of you but please can anyone recommend me a rom where market is working and where the following applications can be installed and used?
- eyesfree suite of applications,
- talkback - the google screen reader for android,
- tts service.
All possible help is already appreciated.
Click to expand...
Click to collapse
i am on mcr3.0, i looked in the market, i can find 8 apps for eyesfree, tts is one of these. i didn't try to install one of these, but usually it works. the search for talkback returned nothing.
not that i want to be rude, but wouldn't you be better off with another phone if you are blind? i can not imagine a touchscreen only phone would be suitable for someone who is not able to see... especially because there are great devices out there that have a full qwerty keyboard, and come with android 2.0 out of the box... imho this would be a better solution.
again, the last thing i want to be is rude, but maybe this was your mistake: you posted in the htc hero section of this forum, the hero is a touch screen only device, including a virtual keyboard on the screen. it has only six buttons and a trackball, and two rocker buttons for the volume. just to make clear we are talking about the same device
if you are still up for the hero you could try the 2.1 rom from here: http://htcpedia.com/forum/showthread.php?p=30418&posted=1#post30418
best you try for yourself, it has some drawbacks, but maybe in areas you don't need (afaik syncing with exchange does not work for example, which wouldn't be a problem for me...). otherwise it might be worth to wait another week or two, we all are waiting unpatiently for the official eclair release from htc
keep asking if you need to know more, but maybe open a new thread, since your problems are very specific, and might drown between all the newbies question about "how to root my phone".
Hello,
Thanks for your reply and a great attitude.
Yes it may sound strange I have really got HTC Hero here. I know I'll be having problems with virtual keyboard but also I am afraid accessibility features of Android phones are not really such mastered one can use it daily. For example reading emails and content from the web browser is not yet possible. I just want to try how things work and I would also like to touch the virtual keyboard. If I can memorize computer keyboard and use it daily, typewriter keyboard, nokia mobile phone keyboard, then perhaps I might be able to make some use of this too.
I am sory but here are some more questions:
I haven't yet verified with some sighted friends but... is it possible my hero is running even older version of android like Android 1.5? I've based the assumption that it's most likelly running 1.5 because majority of the devices I was reading on the net are running it.
You've been triyng to locate eyes-free applications on the market but you were unable to find talkback. Are you sure you are running newer version of Android than 1.5?
Talkback is supposed to be installed with Android 1.6 andd 2.0 by default and you should be able to find it in the accessibility menu of your phone. I am not sure how well this applies to the custom roms.
Talkback requires google's accessibility api which is reported to be available on Android 1.6 upwards.
To tell you the full story first I've asked on the eyes-free google group whether some accessibility experts from there can help me but no one knowledgeable enough has replied to my query, so I'm trying my luck here then.
Oh I am really excited since I've got really well formed informative reply.
Thanks again
Edit:
Also, I've seen somewhere in the forums here this leaked HTC rom does not support the market. Has this been rectified already? You know if market does not work then most likelly I won't be able to install these applications I am tallking about.
Also you are mentioning possibility to wait a few weeks until HTC guys role out the official update for Hero. Wouldn't that break chances I will be able to root my device later?
Edit2:
Ooops, I should read better next time. Market works on this rom. The problem is paid apps can't be installed which is hopefully not a big issue for me since most of the accessibility enabled applications are free.
Which of the downloads from Hero 21 do I need?
63.18.55.06JU_6.35.09.26) or No Wipe Download. I will need a wipe I am sure but since this link says nowipe I am ehmmm. confused.
pvdeejay,
Unfortunately there is not an 'official' update for Android 1.6, 2.0 or 2.1 as of yet. There are rumours of one coming out soon, but nothing cast-iron yet.
You are correct in that the Hero runs 1.5. It does say it under Settings | About Phone (bottom item on list)| Firmware Version (bottom on list again), although without a working screen reader, there is probably little use in knowing how to find that.
If you did want to upgrade, I'm sure plenty of people could help find a ROM that would suit. The only issue with that is that you would need a rooted phone with a custom recovery image installed. Unfortunately, a lot of the procedures would not be easy for you, as the software that you might need to use to go through the procedure is probably not designed that well for accessibility tools. I don't know what kind of software you are using, but some of the instructions for making goldcards are quite complex, and involve editing some numbers in a 'table' which could be quite difficult for you, I would imagine.
I'm sure a friend would be able to help you out with making a goldcard/rooting if you did want to install a custom ROM (you'll probably be waiting a while otherwise ). They could even root their phone while doing yours (just share the goldcard between the devices).
Nonetheless, there is probably a ROM out there with little removed from it. I'll have a look just now, but you would need to have your phone rooted to do anything just now.
When it comes to rooting and installing custom recovery image. Do you thing the following instructions might work for me?
These instructions don't require a gold card:
- How to Root HTC Hero and Install Amon Ra Recovery Image
- How to install a custom rom on a HTC Hero
Hello,
Here are some numbers I've asked my friend to read from system -> about screen. The phone interface is in czech so I am unable to get some names translated to english, but I believe some of the geeks will understand these identifiers and might be able to help me what is best:
Code:
firmware: 1,5
63.118.55.O6U|6.35.04.25
2.6.27-a5504199
Build number: 1.76.405.6 146733 CL# 47214 release-keys
Software version: 1.0.0.A6288
pvdeejay,
to sum it up:
the hero definitly runs on android 1.5. there are no roms for older android versions, and a few homebrewn for newer versions, as we said already.
i searched for talkbalk on my 1.5 rom, so it is obvious that i couldn't find it...
about rooting of newer roms: it is just a matter of time, sooner or later there will be always methods of rooting a rom. what i meant by waiting is: wait until the official update is out, then wait a few more hours until the first rooted and customized rom is out
@pvdeejay,
I would have to agree with kendong2 that waiting for the official ROM is probably the best idea for you at the moment. There are no guarantees that an unofficial ROM would help, and it would be another user interface to try and learn.
@kendon,
I noticed he has the original, easily rooted version of the hero. IIRC, that is what I had on my G2 (and had the security unlocked bootloader out the box). If that's the case, would pvdeejay be able to 'fastboot boot' a full system img file for the purposes of testing it out to see if it meets the requirements.
The reason I ask is that I've only ever fastbooted my AmonRA recovery (I didn't flash it, because I never felt any need to). I'm guessing you could fastboot a full img, but I'm not sure about the practical issues of where it would be stored in memory...
Sorry guys originally I believed I am slowly getting into the matter and am begining to understand how flashing / rooting / upgrading home brew firmwares works on these phones.
After these 2 posts I feel like a total noob again.
Now again some very concrete questions:
What about these 2 guides I've posted links to?
Can I somehow got [Recovery] [13-Dec-2009] RA-hero-v1.5.2 installed so I will be able to do nandroid backup and then possibly flash some new roms?
Can I really brick my phone by trying to install amon ra?
Originally I thought the process works as follows:
1) get the custom recovery image installed (that's the amon ra in this case),
2) do a nandroid backup which will dump everything usefull on to the memory card,
3) backup and reformat the card,
4) download a rom, rename it to update.zip, put it onto the root folder of the cart, reboot the hero in recovery mode, do the wipe of the data partition, and run update,
5) reboot again and believe it's good.
Also some very significant bit is the thing you are all calling the radio. I am afraid I've not identified this bit thus it's missing in this summary.
Which files will I need to download if I decide to try Android 2.1 community edition 1.8? Are these files I've copied links to a few posts earlier both needed?
Can you please check this list, identify the things I am missing, and make suggestions and corrections why this may not work on my device based off of those number I tried to put down here?
Even if I won't be able to do this right now I'd be happy to get corrections as I can learn something new.
Of course I won't be doing all this on my own. I will ask my bro to read all the stuff to me and we'll do it according to your advices.
To give some bits about me and my computer skills, I believe I am a Windows power user, Basically I do also understand unix, I know what's bash how the files are arranged in a file system, can use command-line tools, telnet, ssh. I am working as a network administrator here so some background is there really.
Hi pvdeejay,
Answers to your questions here.
You can actually use fastboot to 'temporarily' load up the AmonRA recovery image into memory and run it from there. I do that on my phone, for the simple reason that I can't be bothered ) ) to flash the recovery. Once you get AmonRA running, the first thing you should do is make a Nandroid backup. It will be saved to your SD card, so then get the nandroid directory of your card and save it to your PC (just in case!)
So, here's how you'd go about this.
(Make sure you have the android sdk installed, and that adb and fastboot commands are working). USB cable should be plugged in throughout.
Before you begin, put the ROM you want (ie. Android 2.1 community edition 1.8) into the root of the microSD card (a .zip file).
Code:
adb devices
Should list your phone's serial number
Now turn off the phone, and turn it on with the back key held down (the one at the very bottom right of the device).
You should enter fastboot mode. Now type
Code:
fastboot devices
and you should see the serial number again.
Now type
Code:
fastboot boot AmonRA.img
where AmonRA.img is a file in your present working directory that is the filename of the latest custom recovery image. This does NOT flash your phone, it merely runs the image (pretty much as close as you get to risk free, other than sitting there with a tinfoil hat on )
See screenshot of the recovery image here:
http://www.sizzledcore.com/wp-content/uploads/2009/12/RA-hero-recovery-image-500x375.jpg
Make the Nandroid backup by choosing 'Nandroid Vx.x Backup' and waiting a while.
If your ROM needs a wipe first (most new ones do), select Wipe data/factory reset. You will lose all your user data on the device (but you've got a nandroid backup just in case)
You're now good to go. So choose "Apply sdcard:choose zip"
Now select the custom ROM zip file you downloaded. It doesn't even need to be called update.zip! Choose it from the list and push trackball.
Wait for the update.zip to go in. Do NOT turn off the device or pull the battery. First boot can take a very long time (upto 30 minutes). Just keep it plugged in via USB and wait...
As for radios, see http://android.modaco.com/content/h...-24-11-hero-roms-radios-in-update-zip-format/ and look at the section titled radios. The latest one is in bold. It is a .zip file as well, that you use these exact same instructions for to install (don't do the wipe or anything like that. Just install the .zip file)
anon2122 said:
@kendon,
I noticed he has the original, easily rooted version of the hero. IIRC, that is what I had on my G2 (and had the security unlocked bootloader out the box). If that's the case, would pvdeejay be able to 'fastboot boot' a full system img file for the purposes of testing it out to see if it meets the requirements.
The reason I ask is that I've only ever fastbooted my AmonRA recovery (I didn't flash it, because I never felt any need to). I'm guessing you could fastboot a full img, but I'm not sure about the practical issues of where it would be stored in memory...
Click to expand...
Click to collapse
this is correct so far, i did the same, except i installed the recovery. i play a lot with my phone, the installed recovery image with the nandroid backup is the best i have ever seen for a phone...
@pvdeejay
you always write so much...
i try to answer everything:
the two guides you posted are good for your situation. i never tried flashrec, but from what i read it is safe to use. i installed my recovery image through fastboot, the guide is here: http://android.modaco.com/content/h...ng-the-patched-recovery-image-on-your-device/
i have no idea how this works out for you, but my honest suggestion would be that you have someone seeing assisting you, you CAN brick your phone, though it is not likely if you follow the instructions precisely. the process is not very time consuming at all, so you don't need to bother anyone for days of their time.
edit: and now i read your post to the end and saw that your brother will be helping you, so you are on the right track
once you have the recovery installed you can make nandroid backups, and i would suggest that you do this first thing after installing the recovery, better make a backup too much than one too less...
the 5 steps you described are correct, except there is no need to rename the zipfile anymore, you can select any .zip from your sdcard.
the radio part is the number that begins with 63.18.55.06, then comes two letters and then more numbers. as by now the version can be identified by the letters, with JU being the up-to-date one. in general you can say the newer the better, but you have to try for yourself. start with the newest one, if you have problems go back.
thanks this seems to be pretty doable plus I will easily be able to restore the current data backed using nandroid backup.
Which android SDK do I need the latest one?
The commands I need to type are supposed to be typed on the PC or on the phone? I assume on the PC but I just would like to ensure.
Hero21 1.8 community edition has a recommended radio listed in the first post. Is it necessary to install that one as well? What should I install first the actual rom or the radio? Do I need installing radio at all? Should i do the same with radio i.e. renaming it to update.zip and using amonra to install it?
Also will I be able to use this method even if I install another rom (running amonra without actually flashing it)?
Edit:
sorry guys did not realize renaming to update.zip is no longer needed.
Edit2:
is there an easy way on how to access sd card from windows? I can't just remove the card from phone and insert it into my laptop because I don't have the proper adapter. Previously my boss was using the hero and perhaps it would be nice to backup the sd card first.
Edit3:
uhmmm, installing android sdk is perhaps not as simple as it sounds.
I have just seen this article.
I am on a limited gprs internet connection, can you please suggest sdk features I won't need to save some download bandwith?
- you need only the adb binary (thats adb.exe for windows) from the sdk, the rest is not needed for this.
- install the radio from the 2.1community-rom-thread, it is the newest. install the radio first. DO NOT PULL THE BATTERY until the phone has rebooted completely. if you pull the battery during radio upgrade your phone will be dead. it takes a few minutes, do not panic!
- you can copy the contents of the sdcard via the usb-cable, plug it into your pc and pull down the notification bar...
Do I need to run SDK Setup.exe when I have downloaded android sdk for windows?
Or can I simply run that binary from the command-line without the installation?
Do I need any USB drivers so my phone can be recognized?

best mod for elocity A7

My tablet was runnin dexter mod 1.4 with all the patches, buy always had problems with the sd card and the usb thumb and I also had problems running some applications. Right now my A7 is running [mod] update04-19 patched market + google apps and my tablet is working almost perfect. I think this mod is better that dexter mode.
I hope everybody use this mode in their tablets.
Thanks Bestialbub for your great job.
i jus got my elocity a7
i tried to mod mine with the dexter mod 1.41 and mines wont work,
1st- i download the file didn't unzip it then i sent it to the SD card and rename it "update.zip".
2nd- i did the factory wipe/reset then i select to wipe all data
3rd- i select update.zip but i notice an message saying( E. can't read from SD card). i dont know if that is apart of the mod or what.
4th- when it is finish then i select reboot option and when it is done rebooting i get nothing new. can you help me out are do you know something that i might be doing wrong. i also did do the 1.42 patch aswell didn't work. are is there another mod that you can tell me how to get it.
hasn't been tested for application on dexter's rom, though i don't know of reason they shouldn't work. gapps can be flakey like that; actually, the files are all stock as they come from cyanogen, minus my patched market, which doesn't have any reason not to work on dexter's rom and has nothing to to with the installation of the rest of google applications, including the calendar and text messaging services; i introduced no signature issues else it wouldn't install on stock firmware.
what i can suggest, is that if you're doing this under wiped conditions; is that you need to do a "factory reset" in recovery AFTER applying my gapps update.
if you don't do the factory reset, there will be settings put in place by the provision.apk in dexter's rom (not sure if this has changed in 1.42) that may conflict with the setup of google-apps. it didn't w/ the gapps in v1 i ported from dexters rom in previous tests, but i was going for a vanilla install w/out mixed signatures/versions/dates. provision.apk is generally suggested to be removed when google-apps is intended to be installed, and it is by my installer, but not the changes done in the data folders, which is why the wipe is suggested. i think its role is replaced by the googlepartnersetup.apk, but i could be wrong.
theres also some build prop differences; some unnecessary (gsm provider info), some improved (fingerprint for added apps in addition to patched market and added permissions), and the same ones necessary for apps like skype to run.
sorry if that was too much info. i do that.
EDIT: i reviewed my original post, its step *2B*. i did update it to underline it, and provide explanation for its probable necessity.
bestialbub said:
provision.apk is generally suggested to be removed when google-apps is intended to be installed, and it is by my installer, but not the changes done in the data folders, which is why the wipe is suggested. i think its role is replaced by the googlepartnersetup.apk, but i could be wrong.
Click to expand...
Click to collapse
SetupWizard.apk replaces "provision.apk".
bestialbub said:
theres also some build prop differences; some unnecessary (gsm provider info), some improved (fingerprint for added apps in addition to patched market and added permissions), and the same ones necessary for apps like skype to run.
Click to expand...
Click to collapse
Audio fix, which enhances EQUlizer and probably a 10% audio increase, and rotation support for games is another one..
the gsm props were actually very much needed, as Google for a period enabled provider checking, so if no gsm provider was there, you could not activate a google account, so instead of ppl getting lost without MarketEnabler on a clean device, i included it for safety reasons so next time, we're prepared for such checks.. so it all serves a purpose, if you like to know more, XDA has excellent information on those topics.
SetupWizard.apk replaces "provision.apk".
Click to expand...
Click to collapse
thanks for the tip. i did concede i could be wrong, and you're right, i could find that small detail that setupwizard is known to replace functions for provision.apk. the same posts i'm finding on xda and cyanogenmod don't say anything about googlepartnersetup, however, yet its provided with gapps packages..
i also learn from demonstrated and practiced examples..
demonstrated examples i learned from, including your 1.2 rom shows your remove provision.apk and provide googlepartnersetup.apk, then reverse the decision in 1.4, i ASSUME based on signiture issues you had stated (i generally don't have those as i know i can re-use existing containers without having signature issues).
i also learned/ported from various sdk's, including google's sdk for gapp imports, and neither is required, but what is provided is sdksetup.apk.. me seeing a relation from sdksetup for an sdk/emu android device kinda indicates one might want googlepartnersetup as a counterpart on a physical device. (your 1.4 example does prove that doesn't have to be true).. but the google sdk shows that i don't need setupwizard.apk for google services either.
thought i'd relate, since most the general posted information i've seen on xda and cyanogenmod seem like vague gueses at best. though i suspect the people posting this information aren't necessarily the devs working closely with the files. just hobbists and modders making educated guesses like me.
Audio fix, which enhances EQUlizer and probably a 10% audio increase, and rotation support for games is another one..
the gsm props were actually very much needed, as Google for a period enabled provider checking, so if no gsm provider was there, you could not activate a google account, so instead of ppl getting lost without MarketEnabler on a clean device, i included it for safety reasons so next time, we're prepared for such checks.. so it all serves a purpose, if you like to know more, XDA has excellent information on those topics.
Click to expand...
Click to collapse
i was refering to MY gsm provided build prop information, i wasn't ragging on your build prop or rom addons. i followed suit to the gtab tnt modrom and added DIFFERENT gsm provider information than yourself (service provider id, not google client information). but it made no difference in gapps present demonstrated performance as this information DOES NOT (the stuff i provided/borrowed from tntlite) get passed into the android system or database files, as no service provider id is listed when opening marketaccess.apk, as it does on a phone device that does genuinely have this information.
i do concede to the thread discussion, tho, DEXTERS ROM IS THE BEST AND ONLY FULL ROM MOD FOR THE A7 TABLET!!!
my gapps mod is only intended to provide google applications ommitted by the manufacture. nothing more.
thanks for the indirect market patching instructions!
thanks am going to retry and see what happends
bestialbub said:
but it made no difference in gapps present demonstrated performance as this information DOES NOT (the stuff i provided/borrowed from tntlite) get passed into the android system or database files, as no service provider id is listed when opening marketaccess.apk, as it does on a phone device that does genuinely have this information.
Click to expand...
Click to collapse
Had the same issues, so i found the trick to be adding it in the boot.img using the default.prop, and it is added during bootup.. but now we're OT! so let's leave it at that.
a7 installation problem
these are the exat message i got (E:can't open/usb/update.zip)
(E:Can't mount USB:update.zip)
then underneath that it say (Finding update package)
then it say (Wait for 5 second)
(Installation time out)
(installation aborted)
(Formatting MISC)
these are all the thing it say during installation
these are the exat message i got was (E:can't open/usb/update.zip)
(E:Can't mount USB:update.zip)
then underneath that it say (Finding update package)
then it say (Wait for 5 second)
(Installation time out)
(installation aborted)
(Formatting MISC)
these are all the thing it say during installation
why post the same thing every 10 minutes?
.............................
demamalu said:
My tablet was runnin dexter mod 1.4 with all the patches, buy always had problems with the sd card and the usb thumb and I also had problems running some applications. Right now my A7 is running [mod] update04-19 patched market + google apps and my tablet is working almost perfect. I think this mod is better that dexter mode.
I hope everybody use this mode in their tablets.
Thanks Bestialbub for your great job.
Click to expand...
Click to collapse
That is not a mod it's the factory firmware with a patch to get market, I don't see in what way it is better than Dexter mod.
kevinppk said:
these are the exat message i got was (E:can't open/usb/update.zip)
(E:Can't mount USB:update.zip)
then underneath that it say (Finding update package)
then it say (Wait for 5 second)
(Installation time out)
(installation aborted)
(Formatting MISC)
these are all the thing it say during installation
Click to expand...
Click to collapse
When this happen I remove the .zip from file name or just rename the file but most time removing. .zip does the job...

Issues with Accelerometer/Screen Rotation

Before I get shut down for posting about a topic that has been posted before - I am doing this so others can access all the info in one place without having to scour the web/forum/posts.
Firstly let me point out a couple of important topics of discussion:
- You may just have a phone that has a hardware error. If you run through this post and options and you don't have any success, give some serious thought to getting it repaired because no matter how many new rom releases come out it isn't going to fix it.
- Full SELinux Support - If you use TWRP2 they have recently updated to 2.7.0.1 - It's worth reading through the 'Note' listed in the changelog. They talk about how Full SELinux Support is needed for installing Kit Kat roms and some of their older versions didn't support it. (http://teamw.in/project/twrp2)
- Rom and App settings - The Rom has several places to tick/untick screen rotation. Some apps also have screen rotation toggles. The important one is the Rom settings, make sure you have actually turned rotation on. It can be found in the notifications menu at the top of your screen (if you haven't removed it through customisation), also in Settings>Display> which is not to be confused with 'Smart rotation'.
- Smart Rotation - You do not need this turned on for screen rotation to work. In fact I would recommend leaving it turned off as it slows screen rotation down. I'll leave it up to you.
- Samsung Bloatware - There has been some talk on the forum about how removing Samsung apps has caused screen rotation to break. This is possible as several library files are shared. Since you are running a "custom" Rom it's hard to know whether any scripts have been included in the installation that haven't been specifically listed in a changelog.
- Model Vs Region Vs Solution - There are quite a few S4 models available at present. Most of these have hardware differences and the solution that worked for someone else may not work for you. It's good for you to start by learning what the differences are and what components were included in the version you purchased (this will save headaches later).
BACKUP YOUR DATA - I will not be held responsible for any actions you take with your device!
Ok, let's get started with the options/work arounds that you may wish to use and how they work (You will need to have root access):
1. ReInstall the Rom - This is the first place to start. You can usually install over the top of the initial installation without any issues. This would replace any data that may be corrupt from the installation. If you have installed a custom kernel it will install the one that comes with the Rom.
2. Clean install of the Rom - Sometimes we have to strip it all the way back to like-new. This means you would need to Factory Reset the phone (this will remove all apps and sign in data). If you wish to go all the way in cleaning off your device there is a Format option available in TWRP2 and PhilzTouch. Don't format unless you know what you're doing otherwise you could format the EFS data and then you're screwed. Don't say you haven't been warned.
3. a) Install a Library file (through recovery) - This is a script that has been built to replace a library file that is removed when you uninstall Samsung Hub. There is a discussion taking place in the Note3 forum where you can get the file. Be sure to follow their instructions exactly. http://forum.xda-developers.com/showthread.php?p=50099965
b) Install a Library file (through Android) - Using the same ScreenRotation.zip file you can download from the link above, open the zip and save 'libgnustl_shared.so'. You will need to put this file on your phone somewhere you can find it so you can copy it to the correct location and set some permissions. You need root access to even attempt this one, if you are unsure about what you're doing I would proceed with caution. It's not rocket science however you want to make sure that you don't alter any of the other files. You need to place libgnustl_shared.so into the \System\Lib folder. If the file is already there I would rename the old file rather than copying over the top. This just saves you in case anything else goes wrong and you need to go back a step. You need to change the permissions of the file before going anywhere. I used ES File Explorer to move the file and it allows simple change of the file permissions (through properties). It needs to be -rw-r--r-- or if you are using ES File Explorer then it should read Owner: Read & Write, Group: Read, Other: Read. You will then need to boot into recovery and wipe cache and davlik cache (don't confuse this with Wipe: Factory Reset).
4. Install a Stock Rom from YOUR phone provider - Telco's spend time and money ensuring their releases work with all the features of the phone, this is sometimes the reason why they take so long to update their software. Some of these features are Telco specific and others are region specific (hence my comment about being aware of what you have purchased). If you have installed a stock rom and you still have screen rotation issues it is likely (not guaranteed) that there is a hardware issue. In my experience installing a stock unmodified rom often addresses the issues that crop up on custom roms. It's worth testing it for a day or two on stock to ensure it's not intermittent. If you are willing to go to all the trouble you could try installing a custom rom again. I have has success in the past doing it this way. I can only assume that the installation of the stock rom addresses issues with internal components/firmware.
5. Kit Kat Roms - If you have loaded a bootloader that excludes you from installing your carriers stock rom (due to it being Jelly Bean or earlier), there are stock Kit Kat roms you can download in the forum. You won't have the added support of carrier addons and tweaks, however you will still get stock Samsung which is the next best thing.
What to do if none of the above work?
There are two options 1. Send it off for repair 2. Continue to work on it yourself with the help of others on the forum.
If you wish to continue working on it yourself or you have voided your warranty here are some tools to help. You need to take a look at whether your accelerometer is working - This is indicative only (an indicator) and will help you narrow the problem down.
1. In your dialer (phone) put in the following *#0*#
This will allow you to go in and see how the components are responding - You want to take a look at Sensors.
2. Accelerometer Monitor/Test Applications
There are quite a few for free on the market place - They will show you how the X, Y & Z axis are responding to the movement of the phone. Sometimes it is quite obvious when certain axis are not responding at all. Some of these applications will allow you to calibrate the sensors. I am not 100% sure whether these calibration options will work on Kit Kat. If you are speaking with a developer of a custom rom they will often query you for log data, this is code that will help them work out what is going wrong. This doesn't guarantee they will be able to fix it. Not all of the accelerometer apps provide a log but is necessary information you'll need if you decide to go down that path.
(AndroSensor is relatively good - https://play.google.com/store/apps/details?id=com.fivasim.androsensor)
Let me know how you go.

Google Assistant on any Android Phone

This giude was made as i found a method to enable google assistant in your phone..
Requirements:-
A phone with custom recovery
Three files provided below
Android 7.0 or higher (as for now)
All google apps must be either force closed or uninstalled before flashing the files
For this,you have to download the 3 files from this MOD EDIT: REMOVED.
->After downloading puth these files in your phones storage.
->Then,Reboot into recovery..
-> In recovery mode you will not be able to see the third file(tweak.prop)
First,flash GoogleAssistantVelvet.zip
Then,flash GoogleAssistantBuildProp
->After installing Wipe Cache
You Are done..Enjoy The new Google Assistant in your phone,,
F.A.Q
Supported languages by Assistant?
-> English and German as for now.
Will I get OTA Updates?
->Nope,As phones build.prop will be changed to PIXEl
Will it work on Marshmallow??
->i dont know,But i found this thread..You can try and tell me.. Visit this thread.
Working Devices
Almost all Phones.. Tested on Arm64(Redmi Note 3) Arm(Moto X2) x86(zenfone2)..All working fine..
Good Luck:highfive:
Tell Me if i helped...
Who created these files, where are they from? Are these for 32bit or 64bit? I am not sure I would call this a guide. How about some additional information, like what device you have a working version running on. Also, brief as it may have been, upon a little looking around it would appear there is not a one-size-fits-all solution as different devices require different parts of certain apk's. Have you resolved this?
Are all functions of assistant working?
Is OK Google working?
Not tryingto come off harsh, but this seems off somehow. Maybe I shouldn't have looked at your "How to build a custom ROM beginners guide", not exactly building a ROM, more like a coloring book, everything is already there you just slip a picture into the back and now it's 'Your Custom coloring book".
StevetotheH said:
Who created these files, where are they from? Are these for 32bit or 64bit? I am not sure I would call this a guide. How about some additional information, like what device you have a working version running on. Also, brief as it may have been, upon a little looking around it would appear there is not a one-size-fits-all solution as different devices require different parts of certain apk's. Have you resolved this?
Are all functions of assistant working?
Is OK Google working?
Not tryingto come off harsh, but this seems off somehow. Maybe I shouldn't have looked at your "How to build a custom ROM beginners guide", not exactly building a ROM, more like a coloring book, everything is already there you just slip a picture into the back and now it's 'Your Custom coloring book".
Click to expand...
Click to collapse
yeah sure,iwill
Thread closed as this is a copy of this guide: http://forum.xda-developers.com/showpost.php?p=69074667&postcount=112"
The Flash
Forum Moderator

Wifi and bluetooth fix

Hi everyone,
I would have post this in the developer section, but I'm new, so I can't. I'm asking your help because of a problem that seems to hit some xiaomi devices: wifi and bluetooth at one point don't work anymore. Sometimes they decide to work again and after a while, again, the stop working. I tried to change ROMs, the problem seemed to be fixed, but after 1/2 day it comes back. In internet there are files for fixing this specific problem, often called "wifi_and_bt_fix" and you can find them for almost all Xiaomi models. The one I need, having a Redmi 3, is the "ido" one (I can't post link, neither, being knew. But if you want I can post a link to the file I'm talking about).
You have to flash it in EDL mode. But when i try to flash it, all MIflash versions i used, kept giving me the error "0x8000ffff max buffer sector is 32". When i try a newer version of Miflash, the error changes: "index out of the limits of the array". I already tried all version of miflash, on windows 10 and windows 7. I really don't know what to try anymore.
Anybody knows what to do? If the file it's incorrect? o how to solve the main problem with wifi and bluetooth?
(sorry for my english, I'm italian)
Pardon me, don't worry about your English, it's not that bad, at least I'm still understand about your main issue
Btw, could you give us more details about:
1. The type of your phone (I assume IDO, but better to make it sure 1st).
2. The firmware used on your phone, the version of it too.
3. How do you change ROM? Have you perform clean install by deleting the system partition 1st?
From details nb.2 and 3, we could localize if the problem come from software or hardware instead (hopefully).

Categories

Resources