Related
When rooting and flashing custom roms, is there any roms which makes your phone work just the same way as it did before? I mean, does all the roms have support for camera(pictures and filming movies), sync (facebook, twitter, email), and so on?
Will I be able to use my phone as I did with the stock rom I guess the question is.
Getting more and more tempted...
aussieglis said:
When rooting and flashing custom roms, is there any roms which makes your phone work just the same way as it did before? I mean, does all the roms have support for camera(pictures and filming movies), sync (facebook, twitter, email), and so on?
Will I be able to use my phone as I did with the stock rom I guess the question is.
Getting more and more tempted...
Click to expand...
Click to collapse
yes of course, especially if you want to use back HTC sense, then flash the sense-based rom.
Android Revolution HD is recommended by me
The first answer I have... is you want exactly the same phone you have... keep your rom
Normally in most of the build thread the dev list what is working and what is not.
So read the first post you'll know.
Take also into account (and do it anyway) that you better backup your staff before testing any build. CWM give you the ability to backup everything. That's great for testing new builds.
General advice: never trust an electronic device!!!! Backup is the rule. One day or another you will loose your data (wrong manipulation, memory corruption...).
hedayat7 said:
yes of course, especially if you want to use back HTC sense, then flash the sense-based rom.
Android Revolution HD is recommended by me
Click to expand...
Click to collapse
I've read more about it now and found a genius guide in sweedish (I'm norwegian so that's pretty close, haha) and now I'm quite sure I will have to give RHD a go.
But what about the phone's language? All over I mean, in the menus and everything. Will I get a english phone after flashing custom ROM's, or can I just change the language settings ... ?
aussieglis said:
I've read more about it now and found a genius guide in sweedish (I'm norwegian so that's pretty close, haha) and now I'm quite sure I will have to give RHD a go.
But what about the phone's language? All over I mean, in the menus and everything. Will I get a english phone after flashing custom ROM's, or can I just change the language settings ... ?
Click to expand...
Click to collapse
Most (if not all) roms based on WWE stock roms have european languages. (At least swedish and norwegian)
peace!
The rom you were thinking of trying definitely has norwegian. Tried it a few days ago with swedish.
Great I can't sit on my hands anymore... *jumps into it* Wish me luck! I hope everything goes the way it's supposed to. I've used Visionary and Titanium Backup to freeze some apps, but that is as far as I've gone... But seems like that wasn't quite enough, if I can get more benefits out of the great phone, I want them
Will the facebook/gmail sync work with RHD? It doesnt say anything about it in the thread. What about the themes for the ROM? They wont override any language-settings or what?
Done! Now I will have to seriously clean up my SD card, as I did double backups of everything, including the stock rom, nandroid backup(?), app, system/settings backup in titanium backup. And I have to check if I will have to install a new radio.
I did. *installs new radio*
Supposedly the new firmware released last week added some new EYE features to the Camera like the ability to use both cameras at once to take a photo of yourself overlayed against whatever the main camera can see. I've had a look through the Camera app but can't see any of the new options in there. Where are they hidden?
knightnz said:
Supposedly the new firmware released last week added some new EYE features to the Camera like the ability to use both cameras at once to take a photo of yourself overlayed against whatever the main camera can see. I've had a look through the Camera app but can't see any of the new options in there. Where are they hidden?
Click to expand...
Click to collapse
The features aren't in the firmware, they are in the camera apk in the new 4.4.4 ROM. Firmware doesn't contain that kind of stuff.
xunholyx said:
The features aren't in the firmware, they are in the camera apk in the new 4.4.4 ROM. Firmware doesn't contain that kind of stuff.
Click to expand...
Click to collapse
Ok, replace "firmware" with "ROM" (which is also incorrect) or whatever nomenclature you prefer, I'm still unable to find the new features that are supposedly in the new Camera app.
knightnz said:
Ok, replace "firmware" with "ROM" (which is also incorrect) or whatever nomenclature you prefer, I'm still unable to find the new features that are supposedly in the new Camera app.
Click to expand...
Click to collapse
That's because it is firmware. It isn't the camera apk.
The camera app isn't a part of firmware. Two totally separate things.
The 4.4.4 ROM update contains the camera apk. The firmware does not.
If you need further assistance understanding the difference, please use google.
If you want the new camera stuff, flash a 4.4.4 Sense based ROM.
Also, replacing the words is not what I did. I am correct. THEY ARE TWO SEPARATE THINGS! Not nomenclature.
You are asking for help and I offered it.
Keep being rude like that, and no one will want to help you.
xunholyx said:
That's because it is firmware. It isn't the camera apk.
The camera app isn't a part of firmware. Two totally separate things.
The 4.4.4 ROM update contains the camera apk. The firmware does not.
If you need further assistance understanding the difference, please use google.
Click to expand...
Click to collapse
Part of the problem with the terminology, is that on any other platform, that which is called a "ROM" on Android would be considered either "Firmware" (e.g. iPhone IPSW "Firmware") or a combination of that and just "Software".
I'm quite aware of the difference of the various partitions etc. When HTC themselves refer to a complete OTA (which includes bootloaders, radio's etc and all the other "firmware" components, as well as updated apps for the System partition), merely as a "Software update", the naming conventions get very blurry.
For the sake of argument in this case, yes, the new Camera.APK is provided in the updated "ROM". As it turns out, apparently the functionality is in the update, but another separate update to the new Camera and/or Gallery apk's is required from HTC to make all the new features available, some of them are in there now.
I fail to see how my comment could be considered rude, but if I've somehow offended you, then I apologise.
knightnz said:
Part of the problem with the terminology, is that on any other platform, that which is called a "ROM" on Android would be considered either "Firmware" (e.g. iPhone IPSW "Firmware") or a combination of that and just "Software".
I'm quite aware of the difference of the various partitions etc. When HTC themselves refer to a complete OTA (which includes bootloaders, radio's etc and all the other "firmware" components, as well as updated apps for the System partition), merely as a "Software update", the naming conventions get very blurry.
For the sake of argument in this case, yes, the new Camera.APK is provided in the updated "ROM". As it turns out, apparently the functionality is in the update, but another separate update to the new Camera and/or Gallery apk's is required from HTC to make all the new features available, some of them are in there now.
I fail to see how my comment could be considered rude, but if I've somehow offended you, then I apologise.
Click to expand...
Click to collapse
I'm a little cranky today. Sorry. I'm not offended, just an *sshole. Cheers!
I have a Pumpkin KD-C0109-US-A HU. It is a single DIN in which the android screen rolls out and flips up. I addition to the screen it has a radio LED display that shows data like input source, RDS etc. The problem is that when I install Malaysk custom firmware, the radio LED's never indicate that the upgrade process is completed. The letters INIT and the recovery mode graphics continue indefinitely even though the radio works and Malaysk's version of Android functions well. Is there some incompatability between the firmware and the MCU for this type of dual display arrangement? The MCU is MTCB-KLD5-V2.77. Is there a work around? Thanks.
The MTC apps are the ones that interface with the hardware. I'd suggest trying to extract them from stock rom and then install to custom rom
Brendo said:
The MTC apps are the ones that interface with the hardware. I'd suggest trying to extract them from stock rom and then install to custom rom
Click to expand...
Click to collapse
We need to first find a working stock ROM that hasn't been flashed over! Most of us flashed MalaySK before realizing that the LED wouldn't work, and don't have a proper image backup of the stock ROM.
That said, on the other thread, someone pointed out that the factory image available for download at http://huifei.fs-fileserver.de/cont...D 4.4.4/800x480/KLD 800x480 20150820 Factory/ restores functionality.
That's funny, because that is basically the same base that MalaySK has been using!
I have diffed that ROM with MalaySK's ROM. One difference that might bear investigation
MTCOEM3.APK -> on the "working" Rom.
MTCOEM4.APK -> on MalaySK. So obviously MalaySK is *NOT* based exactly on the rom linked above. It has a "newer" MTCOEM, which one would think wouldn't remove support for a relatively new feature? However, it's possible that MTCOEM3 would fix the problem.
There are a lot of edits of course done by MalaySK so I can't tell what he's done -vs- difference in the base Roms.
However, they ARE slightly different builds despite having the same build# according to build.prop:
MalaySK:
# Do not try to parse ro.build.description=rk3188-eng4.4.4 18092015.12:05:40
ro.build.description=rk3188-eng4.4.4 18092015.12:05:40
Stock:
# Do not try to parse ro.build.description=rk3188-eng4.4.4 20082015.17:14:44
ro.build.description=rk3188-eng4.4.4 20082015.17:14:44
Although both are labeled as 20150820, you can see that the actual build description is later on the second ROM.
Note (Probably important): I did thankfully screenshot my stock firmware before updating, and my flip-out KLD unit did indeed ship with 20082015.17:14:44... So even though I haven't tried it, I'm willing to bet money that it will indeed fix the issue as the other user has stated. The question is - what's different in those two builds? I don't have an original of 18092015.12:05:40 to diff against the other. But I bet MalaySK does.
I'm also curious if this ROM: EONON2_rk3188_p(20151019).rar (from the factory firmware thread) will operate the LED?
I have been out of the ROM developing game for several years, so I'm rusty on all this, however. Hoping MalaySK can find something obvious, but if not, I'm working on it.
lotherius said:
We need to first find a working stock ROM that hasn't been flashed over! Most of us flashed MalaySK before realizing that the LED wouldn't work, and don't have a proper image backup of the stock ROM.
That said, on the other thread, someone pointed out that the factory image available for download at http://huifei.fs-fileserver.de/cont...D 4.4.4/800x480/KLD 800x480 20150820 Factory/ restores functionality.
That's funny, because that is basically the same base that MalaySK has been using!
I have diffed that ROM with MalaySK's ROM. One difference that might bear investigation
MTCOEM3.APK -> on the "working" Rom.
MTCOEM4.APK -> on MalaySK. So obviously MalaySK is *NOT* based exactly on the rom linked above. It has a "newer" MTCOEM, which one would think wouldn't remove support for a relatively new feature? However, it's possible that MTCOEM3 would fix the problem.
There are a lot of edits of course done by MalaySK so I can't tell what he's done -vs- difference in the base Roms.
However, they ARE slightly different builds despite having the same build# according to build.prop:
MalaySK:
# Do not try to parse ro.build.description=rk3188-eng4.4.4 18092015.12:05:40
ro.build.description=rk3188-eng4.4.4 18092015.12:05:40
Stock:
# Do not try to parse ro.build.description=rk3188-eng4.4.4 20082015.17:14:44
ro.build.description=rk3188-eng4.4.4 20082015.17:14:44
Although both are labeled as 20150820, you can see that the actual build description is later on the second ROM.
Note (Probably important): I did thankfully screenshot my stock firmware before updating, and my flip-out KLD unit did indeed ship with 20082015.17:14:44... So even though I haven't tried it, I'm willing to bet money that it will indeed fix the issue as the other user has stated. The question is - what's different in those two builds? I don't have an original of 18092015.12:05:40 to diff against the other. But I bet MalaySK does.
I'm also curious if this ROM: EONON2_rk3188_p(20151019).rar (from the factory firmware thread) will operate the LED?
I have been out of the ROM developing game for several years, so I'm rusty on all this, however. Hoping MalaySK can find something obvious, but if not, I'm working on it.
Click to expand...
Click to collapse
I think that you are on the right track but I lack the expertise to figure this one out. I am the someone that pointed out the factory image that solved the problem. I will help in any way that I can to get this problem solved.
windseye said:
I think that you are on the right track but I lack the expertise to figure this one out. I am the someone that pointed out the factory image that solved the problem. I will help in any way that I can to get this problem solved.
Click to expand...
Click to collapse
I think the best option would be to run the factory firmware with a 2gb partition. Will test that over this weekend.
I confirmed that the latest "factory firmware" on the HuiFei unit (20150821) functions correctly with the LED display on our single-DIN KLD units. Others reported that the 20150820 download from the same site works as well.
MalaySK uses a 20150820 base that has a slightly earlier timestamp by a few hours. So either his earlier build doesn't support it, or one of the changes he has made has broken support for the LED.
Our units ship with the later 20150820 build and 20150821 build that has been confirmed to be working from the HuiFei firmware site (http://huifei.fs-fileserver.de/cont....4/800x480/KLD 800x480 20150821 DSA Modified/). The 20150821 (dunno about the 820) already has the 2GB partition mod and root, so it's ready to roll.
I don't think I'm going to test further, as I installed the 20150821 from DAS and it has the 2GB partition I wanted, and everything is working. I didn't try the newer build (20151019).
But with that said, I think this thread isn't going to be necessary as the standard KLD Roms *DO* support our single-DIN LED Display - it is just MalaySK that does not.
Yep, it all comes down to narrowing down what software is required to interface
I wonder if you installed working rom and replaced mtcradio with stock or custom version (or one from malaysk rom) if led still works. If it does, there must be another app in the background required (eg. mtcoem)
Brendo said:
Yep, it all comes down to narrowing down what software is required to interface
I wonder if you installed working rom and replaced mtcradio with stock or custom version (or one from malaysk rom) if led still works. If it does, there must be another app in the background required (eg. mtcoem)
Click to expand...
Click to collapse
Well personally I got it working buy using one of the "stock" roms with 2gb, so I'm satisfied for now. If anyone else wants to play with it further they can.
Found a workaround for the "Init- Problem" of the custom ROMs of MalaySK:
Install the Custom ROM normally.
Then edit the file "build.prop" in the /system directory:
- find the line "ro.product.customer=HCT4" and replace HCT4 with KLD
- reboot device
with that my display was showing the correct things again :laugh:
(tested with the ROM from 17.03.2016)
hope that helps
mgh33 said:
Found a workaround for the "Init- Problem" of the custom ROMs of MalaySK:
Install the Custom ROM normally.
Then edit the file "build.prop" in the /system directory:
- find the line "ro.product.customer=HCT4" and replace HCT4 with KLD
- reboot device
with that my display was showing the correct things again :laugh:
(tested with the ROM from 17.03.2016)
hope that helps
Click to expand...
Click to collapse
Great solution. Definetly will try that.
Any ideea if the MCU for this one-din units is a special one? I installed MTCB-KLD-V2.78 from (HuiFei Server) and now I cannot control the flip-up screen. My unit is MTCB KLD one-din with Android 4.4.
Hey forum!
I'm looking for the best combination of some key functionality:
Stability
Camera (activate/snap with button as on stock ROM), is this possible out of stock ROM at all?
BLE (Bluetooth Low Energy) support but I guess that it is supported in newer ROM versions? Hardware should support it.
Most amount of memory/space available for apps, more than stock ROM possible?
Has to be Android 4.3 at least
Any suggestions of a good ROM which fulfills the above?
TIA!
If u want stability + camera + memory for apps and games then u need a ROM that is naosp 6.0 by mickybart's
but u need to reparation your device memory table to use this ROM
verma.arun833 said:
If u want stability + camera + memory for apps and games then u need a ROM that is naosp 6.0 by mickybart's
but u need to reparation your device memory table to use this ROM
Click to expand...
Click to collapse
Sounds great!
I have a couple of follow-up questions that I hope someone can answer quite quickly:
1. Should I choose version 5 or 6 (I just want the functions I listed and speed and stability are important)?
2. I understand that I need to re-partition the phone but does that apply to version 5 as well?
3. Is there a *complete* guide if you're on stock ROM and have done zilch/zero/nothing yet to the phone?
Thanks!
Kingpin! said:
Sounds great!
I have a couple of follow-up questions that I hope someone can answer quite quickly:
1. Should I choose version 5 or 6 (I just want the functions I listed and speed and stability are important)?
2. I understand that I need to re-partition the phone but does that apply to version 5 as well?
3. Is there a *complete* guide if you're on stock ROM and have done zilch/zero/nothing yet to the phone?
Thanks!
Click to expand...
Click to collapse
Bump... anyone?
Kingpin! said:
Bump... anyone?
Click to expand...
Click to collapse
Bumping again... still sitting with crappy stock ROM If someone could reply that would awesome - thanks a lot!
Kingpin! said:
Sounds great!
I have a couple of follow-up questions that I hope someone can answer quite quickly:
1. Should I choose version 5 or 6 (I just want the functions I listed and speed and stability are important)?
2. I understand that I need to re-partition the phone but does that apply to version 5 as well?
3. Is there a *complete* guide if you're on stock ROM and have done zilch/zero/nothing yet to the phone?
Thanks!
Click to expand...
Click to collapse
1. Choose version 6, it has more updates.
2. Nope, it doesn't apply to version 5.
3. You wouldn't find a complete guide in one place, but I can give You pointers here which will lead You to correct searches.
Rooting : use towelroot app. Not available on playstore, search for "towelroot by geohot". It will root Your phone.
Backup TA partition: backup Your TA partition using tool here.
Unlock bootloader : Link.
Then try following the guide from respective ROM thread to flash the ROM!
I am also in the exact same situation, before I start though I was wondering if there is a way to "easily" back up and restore sms messages & whatsapp messages (along with pictures, though I can copy all the pictures easily on the PC and restore them - but I am unsure if this places them back in the correct order etc) - the rest should be easy to backup and restore just not sure about these 2
thanks in advance
p.s. @verma.arun833 & @Mirhawk
as per the original post I am looking for the most STABLE rom out there to date that is android V4.3.1 or higher - I am also a complete noob too and the easier the better but priority is stability - is naosp 6.0 the best choice here still?
Yup naosp 6.0.1 is best and stable at the moment and updated tooo bro try that ?
androiddude666 said:
I am also in the exact same situation, before I start though I was wondering if there is a way to "easily" back up and restore sms messages & whatsapp messages (along with pictures, though I can copy all the pictures easily on the PC and restore them - but I am unsure if this places them back in the correct order etc) - the rest should be easy to backup and restore just not sure about these 2
thanks in advance
p.s. @verma.arun833 & @Mirhawk
as per the original post I am looking for the most STABLE rom out there to date that is android V4.3.1 or higher - I am also a complete noob too and the easier the better but priority is stability - is naosp 6.0 the best choice here still?
Click to expand...
Click to collapse
You can backup Your sms using this app, I use it and it is the best so far. For WhatsApp, backup using the in app backup and copy the WhatsApp folder from internal storage of phone to PC. Then after flashing the new ROM, copy the WhatsApp folder back to internal storage, install WhatsApp and it will automatically restore it.
And yes, nAOSP 6.0 is still the preferred ROM as it is stable as of now and is receiving constant update. If You want extremely stable but above 4.3.1 ROM, then I would suggest last updated version of Carbon ROM(4.4.4). It is of KitKat version, but has many features and doesn't require re-partitioning of device.
I still get lots of use out of my SM-P600, but I'm hitting a bit of a problem with free space.
I use OneNote combined with the S-pen as my note-taking combo of choice and I have extensive notes. OneNote doesn't have the ability to save notebooks to the external SD card and I work offline a lot, so can't readily open/close notebooks from the cloud. The point is, I'm now struggling a bit for free space on the device.
My newest phone (Android 6.0.1) has the ability to 'integrate' external sd memory into the main device memory.
Is that a firmware feature, or is it hardware?
Would upgrading my P600's firmware give me this functionality and let me have a lot more space to play with?
If so, what ROM upgrade should I use?
Sorry if these are stupid questions, but a pointer in the right direction would be much appreciated.
Thanks in anticipation.
John
If you are interested in rooting and installing Xposed framework, there is an Xposed module called XInternalSd that you can use.
That said, if you aren't familiar with the risks of root, xposed, flashing, etc, be sure to read up on it all a bit first.
Xda module thread: https://forum.xda-developers.com/xposed/modules/xposed-disablesignaturecheck-t2789267
Xposed module page: http://repo.xposed.info/module/com.pyler.xinternalsd
Good luck, and I hope this helps!
G'day John
Both Marshmallow & Nougat have the ability to integrate the sd as internal memory but you may need to install a custom ROM to achieve this. This will most likely involve you losing data. I'm a novice myself but so I am happy to lose data and reformat and start fresh, but there may be utilities to back up such things.
i recently installed Lineage OS myself but a host of issues so I then went the AOSP build and I am really happy with that, if you want to know how to do that I am happy to help.
Thanks kypreo,
I wasn't sure if it was a default feature or custom to certain suppliers, so that's good to know.
Also good to hear that some builds have issues and are, perhaps, to be avoided.
I've had a bit of a clear-out of some less-used apps, so the pressure's off a little. But I may well go down the AOSP route you suggest.
John
jko said:
Thanks kypreo,
I wasn't sure if it was a default feature or custom to certain suppliers, so that's good to know.
Also good to hear that some builds have issues and are, perhaps, to be avoided.
I've had a bit of a clear-out of some less-used apps, so the pressure's off a little. But I may well go down the AOSP route you suggest.
John
Click to expand...
Click to collapse
I went down that route and so far so good, sometimes its just dumb luck. To alleviate some file issues use an app called cc cleaner to ease off some system files to give you some breathing room. You can also move off app data on apps onto the SD card as well. just be aware once the apps update they go back to the internal storage sometimes so you will need to move them again.
Another reason as to why I went to a custom ROM.
Soks
Need link to download the AOSP ROM
kypreo said:
G'day John
Hi, sorry to hijack the thread. I have the 3g variant and have tried both Lineage 13 as well as 14.1 and experience random reboots, crashes and hanging. I am back to stock Touchwiz Lollipop 5.1.1 as of now but would be happy to try out AOSP rom. Can you please provide me with the link to download the rom?
Click to expand...
Click to collapse
chudu1 said:
kypreo said:
G'day John
Hi, sorry to hijack the thread. I have the 3g variant and have tried both Lineage 13 as well as 14.1 and experience random reboots, crashes and hanging. I am back to stock Touchwiz Lollipop 5.1.1 as of now but would be happy to try out AOSP rom. Can you please provide me with the link to download the rom?
Click to expand...
Click to collapse
If you are back with stock firmware you are already with an AOSP rom...
Click to expand...
Click to collapse
chudu1 said:
kypreo said:
G'day John
Hi, sorry to hijack the thread. I have the 3g variant and have tried both Lineage 13 as well as 14.1 and experience random reboots, crashes and hanging. I am back to stock Touchwiz Lollipop 5.1.1 as of now but would be happy to try out AOSP rom. Can you please provide me with the link to download the rom?
Click to expand...
Click to collapse
Hi mate
Sorry for the delay, please see links below:
https://forum.xda-developers.com/ga...om-android-source-project-19-11-2016-t3503423 (rom gapps)
https://gapps4android.wordpress.com/2016/03/20/gapps-package-comparison-which-to-choose/ ( a guide to select which gapps to use)
Be aware you need to root the original rom and install TWRP 3.0.0 aqnd above. Install the AOSP rom but do not reboot, install Gapps because if you reboot you lose TWRP and won't be able to install Gapps. I had to go to the original and do it from scratch.
Goodluck Soks
Click to expand...
Click to collapse