yashsingh1/xdaforums huggingface dataset:
[Honor 7 Android Development] Icetea:
but funny is....

i can boot with the new boot anim after installing it many times. But if i make a TWRP backup and after than a cust recovery, it never shows this boot anim any longer! The anim was copied to /cust/preinstalled/public/media
[Honor 7 Android Development] m_esser:
Sounds curious :confused: ... I don't know which version of TWRP you are using (offical one or the rc3-version) but I would switch to the other one and test it.

Best regards

m_esser
[Honor 7 Android Development] memht:
Their MD5 values are equal guys. I checked it for you.

370 = Finland Full Rom

371 = Europe Full OTA

F7D4EBB9E7F73CBE7288071ACBC675BF
[Honor 7 Android Development] DigiGoon:
[MENTION=5300098]Speedo.thc[/MENTION] [MENTION=7354493]m_esser[/MENTION] : Just checked UPDATE.APP of B371 incremental update.zip, sorry to say but there is no 3rdmodem.img file there,

[MENTION=6142732]non-toxic[/MENTION] : bootanimation.zip resides in since Marshmallow update:

/system/etc/media
[Honor 7 Android Development] m_esser:
I know that and that was the reason why I have mentioned above that I have no clue where Honor stores that image. But if you look into the updater-script file you will see that there is a statement to flash the partition /3rdmodem.

But let's come to an end with this discussion - this partition is quite small and it does not hurt anybody if it will be updated.

Great - I have just learned a bit more :D.
[Honor 7 Android Development] DigiGoon:
[MENTION=7354493]m_esser[/MENTION] : You said "(probably hidden in the file UPDATE.APP)", so I thought maybe you didn't checked it so. :)

And yeah I checked that there is a line of updating 3rdmodem.img but like yourself I'm also confused, as I can't find that partition anywhere in the incremental update.zip :)

No worries, well I encourage you all to do the investigation and not end this, we will know more about it by researching only. :)
[Honor 7 Android Development] Speedo.thc:
Hello, installed with update.app, extracted with wanam app, which is more easy than DD script but do the same... right/wrong is not the problem, I have the same respect for non_toxic, t_rider, Yoda, paulobrien , m_esser, and yourself, all of us want to provide a good experience with honor 7.

Envoyé de mon PLK-L01 en utilisant Tapatalk
[Honor 7 Android Development] DigiGoon:
[MENTION=5300098]Speedo.thc[/MENTION] no worries buddy, we all are here to do the same, and I meant that I can't say that one of you is wrong because you both know what you are doing that's why. :)

And I asked if you used dd is because, maybe the partition gets modified somehow after the update is installed on the phone, but then again another question: Why then there is no diff between the B370's 3rdmodem and B371's? this is getting weird man. :D :D
[Honor 7 Android Development] m_esser:
I agree - that is strange :confused:. Of course I didn't want to prevent somebody from further investigations but from a ROM related distribution perspective I think that integrating the partition into a ROM is the more reliable way currently (as long as the issue isn't solved).

Best regards

m_esser
[Honor 7 Android Development] memht:
It's same because of B371 OTA update doesn't have 3RDMODEM.IMG :confused: It uses B370's ones. In OTA updates (not for beta ones), there are no main files which belongs to full roms.
[Honor 7 Android Development] Icetea:
we are talking about B180 because i have returned to lollipop since a few weeks!;)
[Honor 7 Android Development] DigiGoon:
Yes yes go ahead, put it inside its a small partition as you said and it will be good as we don't want to delay the release of H7CROM :D, but the question is more confusing. :D We'll investigate it later, no problemo! :D

---------- Post added at 01:22 PM ---------- Previous post was at 01:21 PM ----------

You didn't mention that you were talking about which version, if you need answer specific to your version, always specify it first rather than just diving in with a question without giving info.
[Honor 7 Android Development] Icetea:
anyway, i had this error on MM too: After recovering my "cust" partition with TWRP (modaco rc3!) , i sometimes lost my animation. It is inside /cust/system/media, has the 644 for right management and does not work. Don’t know why.:p
[Honor 7 Android Development] DigiGoon:
As I said since Marshmallow bootanimation.zip lies in

/system/etc/media

try putting your bootanimation.zip there. :)
[Honor 7 Android Development] m_esser:
To be honest - I don't know why this happens but probably you should strive the official version of TWRP instead of rc3. I am not aware of the exact differences both versions have but that's the only option that is currently coming into my mind.

Best regards

m_esser
[Honor 7 Android Development] Speedo.thc:
Hi, for me it's related to broken symlink. When bootanimation live in system, no problem like this.

Envoyé de mon PLK-L01 en utilisant Tapatalk
[Honor 7 Android Development] adxuser:
Thanks for good work and a hiper-ultra-jumbo-turbo configurable rom but of course it should be last which you're posting here.

Having allegedly some cooking skills could you quickly clear this mess with your thread in wrong place and find the place where it belongs?

br
[Honor 7 Android Development] m_esser:
I am not an English native speaker and your post sounds for me very aggressive ... I can only take notice of it. If you don't like it please simply ingore it.

m_esser
[Honor 7 Android Development] essmgus:
Yes the rom is very big but it is the first rom that enables me to configure my phone like I want it. Thanks again to m_esser!

The wrong place is explained in post #32
[Honor 7 Android Development] DigiGoon:
I think he was just trying to ask to put this thread on the correct section, maybe he didn't read post #32. :) :D
[Honor 7 Android Development] m_esser:
Probably you are right ... and might be that I didn't find the best words as well ... that's something that can happen when not-native-speakers are communicating.

Anyway, I have uploaded version 0.12b(eta) with the following changes:

± DigiKernel updated to v1.1 - now with init.d support - Thx to [MENTION=5391886]DigiGoon[/MENTION] (phase 1)

± language files for Aroma Installer updated and partly restructured (phase 2)

± updated all apps (phase 1 and phase 2)

Best regards

m_esser
[Honor 7 Android Development] DigiGoon:
awesome buddy!! :D
[Honor 7 Android Development] m_esser:
Uuups - and suddenly the thread is moved to AD section!

Thanks a lot to [MENTION=2731014]SREEPRAJAY[/MENTION]

Best regards

m_esser
[Honor 7 Android Development] DigiGoon:
Congrats!!! on getting a proper Home. :D :) ;)
[Honor 7 Android Development] anonimov:
Sound Control Panel Problem

Hi

I've tested your rom and is great, but i have a problem. When i access to the sound control panel in order to change ringtones notifications, when i press the arrow the sound or ringtone selector it doesn't open. However, with third party apps that need access to the system ringtone or sound selector it opens correctly.

The problem exist also with v11 as v12.

Greetings
[Honor 7 Android Development] Speedo.thc:
Congrats too, it's good news[emoji1]

Envoyé de mon PLK-L01 en utilisant Tapatalk
[Honor 7 Android Development] m_esser:
I have to check that - unfortunately I am currently very busy because of business workload. Maybe that will take some days :(.

[MENTION=5391886]DigiGoon[/MENTION] and [MENTION=5300098]Speedo.thc[/MENTION] : Thanks for your congrats !

Best regards

m_esser
[Honor 7 Android Development] Speedo.thc:
Hello, for the sound problem, if I remember well, it was coz by a .nomedia file inside directory .. just delete it, another could be bad permissions.

Envoyé de mon PLK-L01 en utilisant Tapatalk
[Honor 7 Android Development] m_esser:
Thanks for the hints!

The default ring tones and notification tones are located at /system/media/audio/... In both directories there is no file called .nomedia and permissions are OK as far as I can see now. Because I didn't touch those files for a longer time I assume that this is not the reason.

In the meantime I have executed 3 tests without being able to reproduce this effect. Because of that I assume that this is a side effect caused by an untested set of configuration selections (please see also section "Beta forever (or banana software that matures on users side)" in post 1).

[MENTION=762874]anonimov[/MENTION] :

Please could you send me a PM with an overview which options you have selected during the installation process? I know that there are a lot of options to describe but without your input it will be extremely difficult to find out which combination of selections is causing the effect that you described. Thank you in advance!

Best regards

m_esser
[Honor 7 Android Development] magnea:
Is there any way to got floating menu option in this rom
[Honor 7 Android Development] m_esser:
Floating dock is already integrated in H7cROM. To get it activated you simply have to goto

Settings - > Smart assistance -> Floating Dock -> Floating Dock activate​

That's all.

Best regards

m_esser
[Honor 7 Android Development] magnea:
Thanks i fung it
[Honor 7 Android Development] m_esser:
Hi,

just to keep you in the loop ... I have uploaded version 0.13b(eta) with the following changes:

added support for USB OTG devices (if attached) to store backup and zip files there as well (phase 1)

replaced Viper4Android with the correspondig material design version (phase 1)

using supersu.zip version 2.78 instead of version 2.76 (phase 1)

deleted SuperSu as optional app (phase 2)

updated all apps (phase 1 and phase 2)

Additionally I have to make some comments:

Usage of USB OTG devices::

During my tests with several devices (partly older USB sticks) I had to find out that it might happen that the Honor 7 does not reboot as expeceted when a device is attached to USB OTG. E. g. one of my memory sticks caused a reboot to the bootloader.

Thus I recommend not to reboot with an attached device but to attach it later and to mount it manually. My general impression is that the usage of USB OTG devices for installation purposes is not very reliable (dependend on the device). Because of that I strongly recommend to ignore this option (even if it has been included into H7cROM).

Rooting:

Probably most of you have already realized that the newest version of SuperSU.APK is not in line with Chainfires actual stable version of SU. I have made several tests regarding the versions and at the end I had to recognize that re-installing H7cROM can cause problems when the update to newest version of SuperSU.apk has been done before. My experience is that the step back to Chainfires stable version 2.76 will lead to a "supersu-less" system.

Although I am not happy with that solution I have made the decision to take the newest flashable zip file provided by MMCT.

For further information you can take a look <here>.

Best regards

m_esser
[Honor 7 Android Development] SoulSeekerHS:
I have the same issue. Clean install of the 0.13b (full wipe), with a lot of boxes ticked during installation. Did you figure this one out yet or should I try and remember what options I used? I can use the dummy files to go through the aroma installer without making any actual changes, right?
[Honor 7 Android Development] m_esser:
Curious :confused: ... I thought I would have fixed that with version 0.13b.

In order to enable you to go through the dummy zip file I have uploaded new files to the folder /dummy on mega.nz some minutes ago. The former dummies were a bit older and they didn't have the same menu structure but the new files have an identical menu structure like v0.13b.

It would be very helpful if you could send me a PM with the parameters that you have used. Thank you in advance!

Best regards

m_esser
[Honor 7 Android Development] SoulSeekerHS:
On it.

Another bug just came up though, although I might just be missing something: The phone won't show up as USB-Drive when connecting to the PC, it's just charging. Neither does the notification come up that asks if I want to charge only or browse files. Changing the options myself in the developer options does not help, neither PTP nor MTP make the PC recognize the phone as a drive.

Imported the Dummy files through the mega.nz app and will try and reconstruct my picks.
[Honor 7 Android Development] m_esser:
I assume that you also have switched on "USB debugging" in the developer options? Further I am using the HDB option to connect my H7 to the PC (settings -> advanced settings -> Allow HiSuite to use HDB).

Don't hurry regarding the options that you have choosed ... for today I have to leave here because of business reasons (tomorrow the clock will ring at 3:30h :( ).

Best regards

m_esser
[Honor 7 Android Development] m_esser:
Hi [MENTION=712333]SoulSeekerHS[/MENTION] ,

thanks for you feedback that I got via PM. I will take a look at the scripts next weekend (when I have more time).

Best regards

m_esser
[Honor 7 Android Development] SoulSeekerHS:
Has anyone installed 0.12 or 0.13 and did NOT get the issue of not being able to select Ringtones and such? Anybody willing to send a bit of info what they selected in the aroma installer? Maybe that could help pin point the cause.
[Honor 7 Android Development] essmgus:
I started installing this ROM with version 0.10 up to 0.13 and I never had that problem. Have just run through the installation. This is my configuration now:

- Digikernel

- Stock recovery and TWRP on second recovery partition

- True Phone

- no further keyboard

- ES explorer

- root browser

- all browsers

- HiBackup

- HiCare

- HiSuite

- Theme Editor

- Stockify

- PM Plus

- Tapatalk

- Whatsapp

- WPS office

- Calendar+

- AIMP

- Pulsar player

- Quickpic

- VLC

- Youtube

- Nova Launcher

- Sure remote control

- Faster GPS

- GPS Test

- Here

- Google maps

- Samsung printer service driver

- Google Plus

- transparent widget for clock and weather

- busybox free

- Fontster

- Partitions Backup

- Power Toggles

- Reboot for Huawei and Honor phones

- ROM toolbox

- Terminal emulator

- Timedtoggles

- Titanium backup

- AdAway

- Adobe flashplayer

- Barcode scanner

- Better direct call

- MyLocalAccount

- MyPhoneExplorer

- Qedit

That's it.
[Honor 7 Android Development] m_esser:
Thanks ... that's reducing the "work space" for investigations a bit.

Best regards

m_esser
[Honor 7 Android Development] m_esser:
Just to keep you informed ...

... today I have crashed my Honor 7 (after falling down from a sideboard now the display has a big break and it is displaying nothing anymore).

I will have to wait for the repair service whether other components are defect additionally. Depending on the feedback I will make the decision to repair or not.

So, investigations and support regarding H7cROM are "closed" until further notice :(.

Best regards

m_esser
[Honor 7 Android Development] janfredrik:
m_esser, thanks for this rom!
[Honor 7 Android Development] DigiGoon:
I hope you get your phone working. :D :D :)

Good luck buddy. :D
[Honor 7 Android Development] HonorCasper:
Ohhh.. Unlucky dude, hope u didn't get hurt, and I feel for u about ure phone[emoji20]
[Honor 7 Android Development] m_esser:
Still waiting for a feedback about potential repair costs ... without that I don't have a base to decide what to do - so I will try to check that tomorrow.

Best regards

m_esser
[Honor 7 Android Development] SoulSeekerHS:
Sorry to hear that. Good luck with the repair.

FYI: I have a few spare parts from a defektive phone, in case it turns out you need them. Screen is broken and motherboard has no bootloader, but all other parts should be fine.
[Honor 7 Android Development] m_esser:
Hi,

today I got the feedback from the technician regarding the defect Honor 7. To make it short - it's not worth to repair the device :(.

Buying a new H7 is not senseful for me because in the meantime there are more powerful devices on the market for the same price.

Thus I have made the decision to stop further investigation into H7cROM ... of course with a tear in my eye.

Thanks a lot to all of you who have supported my efforts!

Best regards

m_esser
[Honor 7 Android Development] lionboy33:
Soon there will be no developers left :(
[Honor 7 Android Development] SoulSeekerHS:
To bad, but thanks for all the work so far.

Better luck with the next phone! ;)
[Honor 7 Android Development] xXfuzzXx:
Thx for your time and work on this!

Have fun with your new device ?

Gesendet von meinem PLK-L01 mit Tapatalk
[Honor 7 Android Development] janfredrik:
Hello! I have used this rom for a few months. I gave the Phone to a friend recently and factory restored it. Now Google Play and Gmail are crashing upon launch. Is there a way to add Google Play which is in phase2 without twrp? A simple method would been great.
[Honor 7 Android Development] HonorCasper:
I think u need to flash the Rom again :) or try a factory reset via twrp, i know u said youve done it but try again, it sometimes have a magic effect:) but If anyone know a easier way Please say so:)
[Honor 7 Android Development] m_esser:
Hi,

I think that [MENTION=7384190]HonorCasper[/MENTION] 's approach should help ...

... if not you have still the option to go back to the newest stock rom (downloading the UPDATE.APP file, locating it in folder /dload on the SD card, executing the factory reset via stock recovery and to flash the version with the key combination "power", "volume up" and "volume down").

Best regards

m_esser
[Honor 7 Android Development] HonorCasper:
It don't take that long to reflash Rom;)
[Honor 7 Android Development] janfredrik:
I tried with the dload/update.app but it got stuck on 5℅. Did go back to stock recovery and tried other plk-l01 emui4 files also. Have you experienced this?
[Honor 7 Android Development] HonorCasper:
Are u Still on H7cROM?

---------- Post added at 11:37 AM ---------- Previous post was at 11:32 AM ----------

In that case make sure that its b371 stock recovery, you can Find it in a thread here on xda Just Google it:) and idk if i understood correct but if u need to Go All the way back to stock this is the way:

Flash stock B371 recovery

Then put update.app from stock B371 firmware in dload folder on Sd-card

3 button combo to flash it

And maybe a factory wipe, and that's it:)

It should now boot up as unrooted stock B371 with stock recovery:)

Then u just flash Twrp and you're ready for maybe another ROM or maybe just root :svetius:

U decide:)
[Honor 7 Android Development] janfredrik:
Can I use HONOR_MultiTool to get B371 Recovery? I only got these options:

1: Flash stock Recovery B313_WEU/UK
2: Flash stock Recovery B320_WEU/UK
3: Flash stock Recovery B321_MEA/UAE
4: Flash stock Recovery B330_WEU/UK
5: Flash stock Recovery B370_WEU/UK

And I've been looking in this thread but I cant find full B371. Thank you.
[Honor 7 Android Development] HonorCasper:
Then i would Go for B370 and then see if you get 371 as ota:) can't find b371 myself:(

---------- Post added at 07:32 PM ---------- Previous post was at 07:31 PM ----------

And you can get firmware from hihonor.com or the firmware finder tool:) haven't tried it myself;)

---------- Post added at 08:07 PM ---------- Previous post was at 07:32 PM ----------

I just remembered this one mate:)

http://xdaforums.com/honor-7/general/models-stock-firmware-packages-honor-7-t3448747/page5
[Honor 7 Android Development] janfredrik:
Thank you HonorCasper, I downloaded from Huawei (http://consumer.huawei.com/no/support/downloads/detail/index.htm?id=80786) and flashed :)
[Honor 7 Android Development] HellFish23:
Hello, I cant seem to get xposed to work in this rom. Even with the provided zip I get a bootloop. Can someone help me
[Honor 7 Android Development] HonorCasper:
Yes, maybe if you go to your build prop and edit or add a line called ro.config.hwtheme=0, if you got the line in the prop u just change 1 to 0, and if u can't find it, just add it in the end and reboot in both cases:good:
[Honor 7 Android Development] HellFish23:
Thanks, but I already disabled theme engine during the install of the rom. I did some research and noticed I did nothing wrong. The problem was that the boot took like 10 minutes, and I misunderstood it for a bootloop.... Its working now :D
[Honor 7 Android Development] HonorCasper:
Oh, like that:) sometimes patience is a good advice too:good:
[Galaxy Tab S2 Android Development] schwabe93:
Reserved
[Galaxy Tab S2 Android Development] papampi:
Awesome,

Thanks a lot.
[Galaxy Tab S2 Android Development] Torrentula81:
Maybe redo original post. I was curious what does it contain and still have no clue. You start off with a history lesson. Its like opening movie credits. Everyone wants to fast forward to the actual movie. Then changelogs like that helps any. The Q and A is nice. Wish more people did that. Maybe remove cell phone pics and replace with a tablet since that is what we are using.
[Galaxy Tab S2 Android Development] ojessie:
SM T179 Rom

Hi,

are you considering making a rom for the SM-T719 its the 8" with LTE.

Best
[Galaxy Tab S2 Android Development] anks329:
Are you using the CM device trees and kernels to build this rom? If not, could you link to your source tree?
[Galaxy Tab S2 Android Development] VeEuzUKY:
Samsung is killing me..

I dont want complain, but I have reached a point of moral exhaustion with Samsung that is starting to take me to the idea of abandoning the brand forever. I have already had a streak of bad purchases and poor quality issues with several Samsung hardware in the past, and to say their repair centers are basically a waste of time, is an understatement. They do anything possible not to honor any warranties.

But that is the past and now, the present as it stands is that I am yet to use my Tab S2 T-815 because its still under 5.01 stock TouchWiz lollipop, and there is NO firmware upgrade path to Marshmallow. I bought the tab under the assumption to update it directly to AOSP 6.01, ONLY to find out I get told that I cant do the update unless my unit is already running stock Samsung 6.01 also to start with.

Folks, believe it or not Samsung is STILL not releasing stock 6.01 for my Hong Kong purchased Tab (version T-815C), only Lollipop updates. Ironically, Hong Kong was one of the very first locations where the Tab S2 line was first available for retail when it was launched and now, they dont even care to get it updated. Even the much older, original Tab S is already getting Marshmallow!!! But the S2 NOT! I really cant believe this neglect and lack of support. Its unacceptable.

Id like to recap and confirm if it is INDEED true that I CAN'T jump into this AOSP 60.1 ROM unless I am already on Marshmallow? Or is there a workaround and way to do it? The weeks and months are passing by and I am totally stuck with a Tab on Lollipop that cant get upgraded. If I had known about this, of course I would have NEVER bought the Tab. In my wildest dreams, Samsung would NOT update a current model hardware. This is inadmissible. I am so sick and tired this situation, I cant describe anymore. My frustration and disgust at Samsung has reached overboard levels.

Anyway, thanks for any advice or ideas on what I can try to do to get my Tab flashed and going with AOSP 6.01. There's gotta be away. Thanks again for the input and thumbs up to the developers for this ROM I cant wait to get my hand on:)

Moderator Edit:

A development thread is not the place for this...

Please use the appropriate sub-forum in future.

Thanks
[Galaxy Tab S2 Android Development] alexeyp:
In-call mic level is very low. I tested it with sound recorder app, and it required scaling the level x98 (98 times).

Is there a way to adjust /system/etc/mixer_paths.xml to deal with it?