Hi,
Here is CM-11 (Android 4.4.4) for the kindle fire hdx 7" (THOR). You need a rooted hdx 7" (Thor) device with a firmware < 3.2.4 (3.2.3.2 ideally) and a signed recovery.
Todo
Bluetooth not working
Wifi won't correctly load when disabled at boot, a reboot is required
Minimal headphone volume too loud -> fixed
Incorrect color format in some scenario's ? (YouTube) -> fixed
Changelogs/Downloads
cm-11-20150226-UNOFFICIAL-thor.zip
Updated to amazon 4.5.3 binaries
Fully disable radio for now (thanks Andy-Voigt)
Fix twrp fstab (enabling twrp was breaking system rom to boot)
CM sources updated to 20150226
cm-11-20150219-UNOFFICIAL-thor.zip
CM sources updated to 20150219
cm-11-20150219-UNOFFICIAL-thor.zip
fix minimal video/media volume too high (youtube...)
switch back to tablet build
CM sources updated to 20150110
cm-11-20150108-UNOFFICIAL-thor.zip
Fix thermal engine (should give better battery life and performances)
Fix a lot of proprietary services (proprietary logs, acdb-loader, ril loading ...)
Set media volume steps to 100 instead 15 (allow finer volume control essentially for jack output)
Lowered minimal screen brightness
CM sources updated to 20150108
cm-11-20150107-UNOFFICIAL-thor.zip
Build without "hacks" (add Cuber signing and custom updater-script generation)
CM sources updated to 20150107
Enable telephony (will probably not work)
cm-11-20150101-UNOFFICIAL-thor.zip
use patched boot/recovery, thanks to @vortox
fix wrong color format ! (major bug resolved)
switch to kernel sources
cm-11-20141218-UNOFFICIAL-thor.zip
minors fixes
cm-11-20141217-UNOFFICIAL-thor.zip
fix wifi not reloading
fix overlay/rotation screen tearing
cm-11-20141216-UNOFFICIAL-thor.zip
updated binaries to amz 4.5.2
properly use precompiled kernel and headers (amz 4.5.2)
fix minimal audio volume too high
add safestrap compatibility
Sources
android_device_amazon_thor
android_device_amazon_hdx-common
hardware_qcom_display-caf-hdx
hardware_qcom_audio-caf-hdx
hardware_qcom_media-caf-hdx
I'm sure the community here respects all of the work that you do. My post in the other thread was not intended to "get you in trouble". There are a set of rules that every user has to follow, regardless of their contributions to the community. That being said, when I was a newer member, I accidentally broke the rules a couple of times (nothing major) and didn't want the same to happen to someone else. (I never contacted @Divine_Madcat about your other thread, in case you were thinking I did.)
r3pwn said:
I'm sure the community here respects all of the work that you do. My post in the other thread was not intended to "get you in trouble". There are a set of rules that every user has to follow, regardless of their contributions to the community. That being said, when I was a newer member, I accidentally broke the rules a couple of times (nothing major) and didn't want the same to happen to someone else. (I never contacted @Divine_Madcat about your other thread, in case you were thinking I did.)
Click to expand...
Click to collapse
Yep i was tinking to that... so I'm also sorry. The thing is i spent a lot, lot of time on this port, and Divine_Madcat didn't even give me the time to update the first thread with the needed files/informations and ignore my pm which was an offense to me. Well i have to complies to the rules too but was a little chocked on how the thread got mad. Well, let's hope it won't be the same here. So that said i have no problem with you !
Cpasjuste said:
Yep i was tinking to that... so I'm also sorry. The thing is i spent a lot, lot of time on this port, and Divine_Madcat didn't even give me the time to update the first thread with the needed files/informations and ignore my pm which was an offense to me. Well i have to complies to the rules too but was a little chocked on how the thread got mad. Well, let's hope it won't be the same here. So that said i have no problem with you !
Click to expand...
Click to collapse
While i am sorry you are upset, it was not a slight at you at all. While i do try to keep an eye on XDA while at work, my job does come first and foremost, and i was unable to handle anything here yesterday (what can i say, 12 hour work days suck). As it was, i have literally nothing against you; to be frank, the report on the thread was the first i had even seen.
From my perspective, we had a placeholder thread, which is not allowed, so it was closed. I fully intended to reopen it, but gave my reasons above...
Anyway, i do wish you luck, and i really dont have any ill will to you...
So....
Do we have unlocked bootloader or a root exploit for amazon firmware 4.5.2 soon? And do you have plan to release another for Apollo?
Thanks
tuanda82 said:
So....
Do we have unlocked bootloader or a root exploit for amazon firmware 4.5.2 soon? And do you have plan to release another for Apollo?
Thanks
Click to expand...
Click to collapse
Nobody knows. But there are a few people working on "unlocks" (at least booting an unsigned kernel). Maybe also jcase releases his unlock (which I doubt because of legal issues).
Hi!
I have rooted Kindle Thor. How do I install this nice piece of software?
Like the Nexus rom? Currently I am on 3.2.7...
Thanks
URBANsUNITED
URBANsUNITED said:
Hi!
I have rooted Kindle Thor. How do I install this nice piece of software?
Like the Nexus rom? Currently I am on 3.2.7...
Thanks
URBANsUNITED
Click to expand...
Click to collapse
You need to be on 4.5.2 and rooted.
cyablo said:
You need to be on 4.5.2 and rooted.
Click to expand...
Click to collapse
Mmmmmhhh
Than this rom is basically usless
Who has a 4.5.2 Base and Rooted??? I would do it if I'll get the tools, no fear of a brick
Too bad. But Nevertheless Many thanks for the work and effort!
URBANsUNITED said:
Mmmmmhhh
Than this rom is basically usless
Who has a 4.5.2 Base and Rooted??? I would do it if I'll get the tools, no fear of a brick
Too bad. But Nevertheless Many thanks for the work and effort!
Click to expand...
Click to collapse
There are a few Users which do have an unlocked Bootloader, this Rom is only for these Users, as stated in the first Post.
I decided to make the rom available in case i loose interest in this device (or if i ever die soon). This way when (if) a root exploit is available then you'll be ready to use it.
Ok... So if there IS a possibility to unlock the actual fireos, please give some hints, instead of publishings Roms that one or two users can install, the rest is completely helpless...
Sent from my Nexus HDX 7 using XDA Free mobile app
openWeb74 said:
Ok... So if there IS a possibility to unlock the actual fireos, please give some hints, instead of publishings Roms that one or two users can install, the rest is completely helpless...
Sent from my Nexus HDX 7 using XDA Free mobile app
Click to expand...
Click to collapse
Sharing hundreds of hours of work is helpless/useless for you ?
You know what ? I actually spent the whole day on porting cm-10 to current exploitable kernel for YOU :/
Everybody chill , @openWeb74, i see your point @Cpasjuste , first let me thank you for all your work, I'm pretty sure its a great Rom!
What openweb said was that maybe we should concentrate our efforts in unlocking the bootloader so even greater support can come.
Unfortunately we, the rest of us common mortals (with locked bootloaders) cannot use it.
As you said, this would work if somebody would release the bootloader-unlock , so lets play the waiting game...
The thing is I'm a common mortal like you :/ Like its said on first post, unfortunately, I do not have the tools nor the knowledge to reproduce the unlock, so I share what I can.
I really have to say sorry, if you dont know how to reproduce the hack... Mea culpa. It sounded like the hack is known, but cant be made public because of copyright issues or something like that... Then we have to wait. Nothing is secure when the right person gets a hdx... I have to say, that my actual hdx was rooted with towelroot, even easier than the nexus (less button combinations ) so i didnt expect amazon to be such a **** with newer firmwares.
Sent from my LG-D802 using XDA Free mobile app
Cpasjuste said:
The thing is I'm a common mortal like you :/ Like its said on first post, unfortunately, I do not have the tools nor the knowledge to reproduce the unlock, so I share what I can.
Click to expand...
Click to collapse
Sorry for nagging you about it, but — genuinely asking — how did you do it on your device in the first place?
dear Cpasjuste, thanks for your great work, and how to install this Rom ? I am newbie, so..
OK... So you are a newbie in reading too?
Sent from my Nexus HDX 7 using XDA Free mobile app
I may eventually move to another tablet as I'm loosing interest in this device (because cm is working fine [emoji14]). Would someone be interested to get my device (not for free )?
Related
I tried the latest build of CM7 done by the Atrix Dev Team and it is awesome. Very reliable, fully functional, etc. I figured I'd give a whirl to compiling the real ICS version to see what that was like.
CM9 build system with the appropriate Atrix Dev Team repos in place actually spit out a working ROM. There are a number of issues aside from the general preview state of CM9. I figured I would share them in case anyone else was as curious as me. Apparently, the internal atrix dev teams are well beyond these issues already, so kudos.
Probably related to CM/atrix specific stuff
- Camera and finger print sensor don't work
- Launcher crashes pretty often
- Some openGL demos don't seem to work right (or at all)
- No mounting the SD as USB storage
Probably related to the specific gapps package I used.
- Maps crashes after 3 seconds (signal 11 - native code crash)
- Maps wants to update, but it can't (sharedId conflict if you actually remove maps)
- Earth won't run (missing the earthmobile library)
- Google Voice Search bombs (signal 4 - illegal instruction - currently suspecting the native packages might have some NEON instructions that the atrix cpu doesnt support)
- Calendar will not sync for google or exchange. App loads, but the sync service is failing
- Lots of null pointer exceptions for the NFC stuff in the log.
Anyway, this is just a build of the code that's out there, nothing special done by me. It might be useful for a dev phone or something but not for use on a real day-to-day device. Obviously it doesn't have the google apps embedded in it.
http://www.multiupload.com/XT9QPPQYF1 thanks xploited for uploading
md5: 670068584eb94bf1d660c0450815ad0d
Personally, I had trouble going back to CM7 afterwards, my clockwordmod backups were screwed up (bad boot.img? cross-linked files on the SD card) and I had a very hard time getting back to the good ole working state. Ultimately, I had to restore the partial backup and then reflash the CM7 image + gapps.
So, if you were curious what building a random repo on the web and installing it on your phone would do, then feel free to try and lose all of your data. There are no updates/support for this, etc. It's just a curiosity... what is the state of this stuff right now?
BTW... I am back on CM7/Atrix now which is AWESOME!!!!
Source Code Links:
https://github.com/CyanogenMod/android
https://github.com/Atrix-Dev-Team/android_device_motorola_olympus
Not sure how the dev team would react to this ..we do not want any bricked phones because of this ..there maybe some experimental dangerous code in there in those sources as of now ..not sure though
Hmm... figured since I spent quite awhile getting a build set up, it might be worth sharing. I am happy to take down if it is inappropriate.
Well I am not the best person to answer that ...but yeah thanks for your work.
Eh, I wouldn't be mad about it, but I think it needs more caution. I would just wait. As you say, it kindof screwed with a lot and wasn't very usable, so why flash it? Maybe ok for someone who wants to look at the code, but I wouldn't flash it.
Awesome news man. Thanks for being a lab rat and giving us an update.
Sent from my MB860 using xda premium
Not so much take it down as change the title of the post.
the current internal atrix-dev-team cm9 is way further ahead of this, we have some different patches. this is missleqading as it makes it sound official and is not.
Could you please change the tittle to [KANG] CM9 Test Build by "your name"
and please link to the sources, as is proper practice for open source projects
thank you
samcripp said:
Not so much take it down as change the title of the post.
the current internal atrix-dev-team cm9 is way further ahead of this, we have some different patches. this is missleqading as it makes it sound official and is not.
Could you please change the tittle to [KANG] CM9 Test Build by "your name"
and please link to the sources, as is proper practice for open source projects
thank you
Click to expand...
Click to collapse
and I guess you guys deserve a Xmas break now ...
It's nice to see that! Thanks for your hard work.
I'm looking forward to the CM9
Thank you for this.
!
Anyways, Just out of curiosity... where can you find the official Atrix Dev team's CM9?
The one been worked on by turl is with him, that is not for public release.
Dont forget to tell him merry xmas!
I always forget what kang means.
Sent from my MB860 using XDA App
wrldsuksgo2mars said:
I tried the latest build of CM7 done by the Atrix Dev Team and it is awesome. Very reliable, fully functional, etc. I figured I'd give a whirl to compiling the real ICS version to see what that was like.
CM9 build system with the appropriate Atrix Dev Team repos in place actually spit out a working ROM. There are a number of issues aside from the general preview state of CM9. I figured I would share them in case anyone else was as curious as me. Apparently, the internal atrix dev teams are well beyond these issues already, so kudos.
Probably related to CM/atrix specific stuff
- Camera and finger print sensor don't work
- Launcher crashes pretty often
- Some openGL demos don't seem to work right (or at all)
- No mounting the SD as USB storage
Probably related to the specific gapps package I used.
- Maps crashes after 3 seconds (signal 11 - native code crash)
- Maps wants to update, but it can't (sharedId conflict if you actually remove maps)
- Earth won't run (missing the earthmobile library)
- Google Voice Search bombs (signal 4 - illegal instruction - currently suspecting the native packages might have some NEON instructions that the atrix cpu doesnt support)
- Calendar will not sync for google or exchange. App loads, but the sync service is failing
- Lots of null pointer exceptions for the NFC stuff in the log.
Anyway, this is just a build of the code that's out there, nothing special done by me. It might be useful for a dev phone or something but not for use on a real day-to-day device. Obviously it doesn't have the google apps embedded in it.
http://goo.gl/39NnA
Personally, I had trouble going back to CM7 afterwards, my clockwordmod backups were screwed up (bad boot.img? cross-linked files on the SD card) and I had a very hard time getting back to the good ole working state. Ultimately, I had to restore the partial backup and then reflash the CM7 image + gapps.
So, if you were curious what building a random repo on the web and installing it on your phone would do, then feel free to try and lose all of your data. There are no updates/support for this, etc. It's just a curiosity... what is the state of this stuff right now?
BTW... I am back on CM7/Atrix now which is AWESOME!!!!
Source Code Links:
https://github.com/CyanogenMod/android
https://github.com/Atrix-Dev-Team/android_device_motorola_olympus
Click to expand...
Click to collapse
Thinks for your works,
Come from Chinese thinks!
i shall say this.. if this is behind where the dev team actually is...things are looking good! and btw.. i believe fruitcaker maker works. installed and is now creating;]
edit: yep. it does.
Thanks man very very good work android congratulations for share work whith comunity
Sent from my MB860 using xda premium
it looks very nice but id needs a bit more work to be a experimental daily driver.
ps: to solve the corrupt backup problem just copy the files to your computer before flashing and copy to your phone before restoring.
good luck!
where can I get google apps for this rom? Tryed gapps for CM7 from CM wiki - fail, setup wizard crashes.
try the one on this link
http://rootzwiki.com/topic/11854-romcm9-encounterics-x-beta-2-with-working-radio-401/
good luck!
---------- Post added at 07:52 AM ---------- Previous post was at 07:47 AM ----------
ilya11g said:
where can I get google apps for this rom? Tryed gapps for CM7 from CM wiki - fail, setup wizard crashes.
Click to expand...
Click to collapse
try the one on this link
http://rootzwiki.com/topic/11854-rom...ing-radio-401/
good luck!
For a preview build it looks pretty nice. Surprisingly stable for what it is. Definitely keeping an eye on this, especially since the code is out there to make DIY kangs with.
samcripp said:
The one been worked on by turl is with him, that is not for public release.
Dont forget to tell him merry xmas!
Click to expand...
Click to collapse
Random SamCripp memory....
"We're rapping them, we're rapping them!!!"
Sorry, guess you had to be there.... aahhh memories... nevermind, sorry for the off topic post.
Thanks though for the effort of getting this ported btw.
THIS BUILD IS ONLY FOR PEOPLE WHO WAN'T TO POINT OUT BUGS AND OTHER ISSUES THAT I HAVE NOT MENTIONED PLEASE DON'T COMMENT AND SAY ZOMG WHY DOESN'T CALL WORK OR STUPID CRAP LIKE THAT! AGAIN TESTING ONLY!!
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
IMPORTANT INFORMATION
We'll not support users and answer questions from users which:
- are running a custom kernel
- have flashed mods
- modified system files
- didn't follow our intructions word by word
- are unfriendly
Even if you tell us that your problem is not related to your custom kernel /mod / magic => WE DON'T CARE!
Your mod => your problem!
CHECK KNOWN ISSUES IN SECOND POST
Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/
First time installing CyanogenMod 10.2 to your FIRST, or coming from another ROM:
- Read known issues ans FAQs
- Make sure you're running a proper working ClockworkMod-Recovery
- Copy GApps and CM10.2 ZIPs to your SDCard
- Boot into HBOOT (hold Volume Down at boot)
- Flash the boot.img
- Fastboot flash boot boot.img
- Reboot into recovery via the bootloader menu
- Flash CM10.2 zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
DOWNLOAD:
Google Apps:
http://goo.im/gapps
ClockworkMod Recovery:
If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
Open-Source doesn't mean Out-of-Respect!!!
XDA:DevDB Information
CM 10.1 HTC FIRST, a ROM for the HTC First
Contributors
Lloir
ROM Firmware Required: A Brain
Based On: CyanogenMod
Version Information
Status: Testing
Created 2013-12-09
Last Updated 2013-12-28
At my discretion i may swap to CM10.1 to start with until i get my device (which should hopefully be soon)
THIS IS Work In Progress
NO ETA'S
NO ZOMG WHEN CAN WE HAZ THIZ
ANY OFF TOPIC WILL BE DEALT WITH BY THE MOD'S
NONE OF THAT CRAP
I do not tolerate fools lightly and i will berate you if you act like a complete idiot.
welcome to my thread
3rd
This is just awesome, installing now and will try to report logcats asap; It's really exciting to see a seriously minded dev on these boards. :victory:
just want to point out, this is a headstart for me, pending getting my device.
so as many logcats and kmsg's as possible. those are ULTRA important
Heh, well I might have the first brick. I couldn't boot past the Facebook logo and after reboot my charging indicator fails to show up.
this should be able to flash in twrp ? even though its 4.3 ? or should i switch over to cwm ? which is also outdated
SneakyGuyDavid said:
this should be able to flash in twrp ? even though its 4.3 ? or should i switch over to cwm ? which is also outdated
Click to expand...
Click to collapse
4.3 is fine to flash *sigh* recovery version only need's to be sorted for 4.4+
the issue last night was that i had compiled the build calling the device the operaul instead of the mystsomething or other
You have any words of advice on fixing the qhusb dload error? I really can't afford another phone.
xnerdx said:
You have any words of advice on fixing the qhusb dload error? I really can't afford another phone.
Click to expand...
Click to collapse
im like 9/10 sure that is a hard brick, just buy a broken htc first for like 40 bucks on ebay and swap the motherboard
SneakyGuyDavid said:
im like 9/10 sure that is a hard brick, just buy a broken htc first for like 40 bucks on ebay and swap the motherboard
Click to expand...
Click to collapse
Like I said, can't afford it right now.. It's the holidays and I'm a college student
xnerdx said:
Like I said, can't afford it right now.. It's the holidays and I'm a college student
Click to expand...
Click to collapse
im still unemployed and in high school lol, ask your aunt, uncle or... *cringes* parents?
SneakyGuyDavid said:
im still unemployed and in high school lol, ask your aunt, uncle or... *cringes* parents?
Click to expand...
Click to collapse
Ha I wish I could ask somebody, I have enough to buy this phone new again but that ruins my plans with my significant other. I think I might as well buy a nexus.
xnerdx said:
Ha I wish I could ask somebody, I have enough to buy this phone new again but that ruins my plans with my significant other. I think I might as well buy a nexus.
Click to expand...
Click to collapse
woah woah wait? the rom put your device into dload?
Lloir said:
woah woah wait? the rom put your device into dload?
Click to expand...
Click to collapse
Yes it did, I followed your instructions and wallah. Not my first time seeing a dload error on a phone either so...
xnerdx said:
Ha I wish I could ask somebody, I have enough to buy this phone new again but that ruins my plans with my significant other. I think I might as well buy a nexus.
Click to expand...
Click to collapse
thats what i mean dont spend a heap load, on a new First, keep most of the money for your plans and just try to buy a cheap First thats broken but has a fully functional mobo
xnerdx said:
Yes it did, I followed your instructions and wallah. Not my first time seeing a dload error on a phone either so...
Click to expand...
Click to collapse
jesus..... @jmz said the device bricked easily.....
SneakyGuyDavid said:
thats what i mean dont spend a heap load, on a new First, keep most of the money for your plans and just try to buy a cheap First thats broken but has a fully functional mobo
Click to expand...
Click to collapse
i'am so so sorry....I WILL try and make this up to you i promise
ALL MY BUILDS ARE HALTED UNTIL I GET MY DEVICE
NOTHING HAPPENS FROM MY END... I WILL NOT RISK ANYONE ELSE'S DEVICE
Lloir said:
jesus..... @jmz said the device bricked easily.....
Click to expand...
Click to collapse
Honestly I think it's an htc thing, I had this happen to my htc evita in a similar fashion.
xnerdx said:
Honestly I think it's an htc thing, I had this happen to my htc evita in a similar fashion.
Click to expand...
Click to collapse
it happened to my one v too, just talking to jmz, as he bricked both of his htc 1st's
AGAIN I'AM SO SO SO SORRY
This was unexpected nor did I anticipate this happening
i honestly feel so bad right now....
To my brothers (you know who you are)
Long, long ago...
A small pet dinosaur was left, abandoned and alone. His keepers, it seemed, had more interest in newer, more capable pets. But he eventually met with other dinosaurs, also abandoned, and a man named hephappy...
STATUS: NOT BOOTING
JENKINS SHUT DOWN
NO DOWNLOADS
The purpose of this thread is two-fold, I think. It is meant to be a venue for androidarmv6 (team) ,as most of their development is done off- site. It is also meant to be a place for hard core dinosaur lovers to test this work, and add to it as development proceeds. As androidarmv6 has brought us, the p500 community, through to working CM- 11, now we will start a new chapter, namely CM- 12. At the time of this posting, there have been several successful builds for the p500. But none are successfully booting, as yet.
I can't stress enough that most of this work is experimental, as the newer source code is being adapted to work on these devices. So unless you are okay with a possibly bricked (unusable) phone, don't flash any of these ROMs. Also, I do not have any responsibility or liability in the case that you should damage your phone by flashing any of this firmware. Also, your warranty will be voided. And I do not represent, and am not affiliated with androidarmv6. That said... YOU HAVE BEEN WARNED.
Website:
http://androidarmv6.github.io/
Source code:
https://github.com/androidarmv6
You can watch development as it progresses, or you can sign in and participate here:
http://review.androidarmv6.org/#/q/status:merged
STATUS: NOT BOOTING
JENKINS SHUT DOWN
NO DOWNLOADS
sent from my towelrooted LG L34C using daishi4u bumped twrp 2.8.3.0 and bumped key-boot-recovery kernel
...as he looked back on the sleeping giants, exhausted from their long journey, the wizard Androidmeda new that he had taught them all that he could, and they had all that they needed. But he also knew that they would never be able to survive crossing the mountains into the new land. Only their child would be able...
Well I guess this is it my brothers. Seems that all has been tried, and CM-12 will not be released for armv6 devices. But many thanks to our devs for trying. It's been a long run. Amazing, just amazing.
ibub said:
To my brothers (you know who you are)
Long, long ago...
A small pet dinosaur was left, abandoned and alone. His keepers, it seemed, had more interest in newer, more capable pets. But he eventually met with other dinosaurs, also abandoned, and a man named hephappy...
The purpose of this thread is two-fold, I think. It is meant to be a venue for androidarmv6 (team) ,as most of their development is done off- site. It is also meant to be a place for hard core dinosaur lovers to test this work, and add to it as development proceeds. As androidarmv6 has brought us, the p500 community, through to working CM- 11, now we will start a new chapter, namely CM- 12. At the time of this posting, there have been several successful builds for the p500. But none are successfully booting, as yet.
I can't stress enough that most of this work is experimental, as the newer source code is being adapted to work on these devices. So unless you are okay with a possibly bricked (unusable) phone, don't flash any of these ROMs. Also, I do not have any responsibility or liability in the case that you should damage your phone by flashing any of this firmware. Also, your warranty will be voided. And I do not represent, and am not affiliated with androidarmv6. That said... YOU HAVE BEEN WARNED.
Source code:
https://github.com/androidarmv6
ROMs:
http://jenkins.androidarmv6.org
sent from my towelrooted LG L34C using tapatalk
Click to expand...
Click to collapse
Congrats! Nice preface wording, bro! :good:
Great! and thanks.
I have not been using cm-11. Omni runs better and seems!! to have fewer bugs. Problem with cm is that when newer comes along, older bugs are left there. I guess we all prefer to play with the latest and greatest so not really complaining. My real problem with cm-11 is the special recoveries needed for it.
I would like to try cm-12 builds, but want to be able to get back to the omnirom. How do I get around the recovery changes (would be nice to have a cwm or twrp that asks on bootup: Want TSL? Switch system and data? But for now, I do not want to lose my alternatives or brick the phone.
How to proceed?
BTW: Link points to end-user builds (cm-11). We'll get there.
Dovidhalevi said:
Great! and thanks.
I have not been using cm-11. Omni runs better and seems!! to have fewer bugs. Problem with cm is that when newer comes along, older bugs are left there. I guess we all prefer to play with the latest and greatest so not really complaining. My real problem with cm-11 is the special recoveries needed for it.
I would like to try cm-12 builds, but want to be able to get back to the omnirom. How do I get around the recovery changes (would be nice to have a cwm or twrp that asks on bootup: Want TSL? Switch system and data? But for now, I do not want to lose my alternatives or brick the phone.
How to proceed?
BTW: Link points to end-user builds (cm-11). We'll get there.
Click to expand...
Click to collapse
Thanks, link updated to View/All.
sent from my towelrooted LG L34C using tapatalk
This is great @ibub !
Thanks for taking the initiative of building CM12 for this device, which never seems to grow old.....
The androidarmv6 team is just awesome! Keep up the gr8 work! It's always appreciated!
Waiting for it to boot for now...
D3oDex3D_AyusH said:
This is great @ibub !
Thanks for taking the initiative of building CM12 for this device, which never seems to grow old.....
The androidarmv6 team is just awesome! Keep up the gr8 work! It's always appreciated!
Waiting for it to boot for now...
Click to expand...
Click to collapse
Just to be clear, this is not my work. Androidarmv6 team (mainly androidmeda for p500) compiles these ROMs. Thanks belong to them (him).
sent from my towelrooted LG L34C using tapatalk
Wut? ART isn't compatible with ARMv6, AFAIK.
Casserole said:
Wut? ART isn't compatible with ARMv6, AFAIK.
Click to expand...
Click to collapse
We shall soon see.
sent from my towelrooted LG L34C using tapatalk
CyanogenMod announces official CM12 Nightlies!
http://phandroid.com/2015/01/05/cyanogenmod-cm12-nightlies/
Do not even expect P500 on the list!
EDIT:
CyanogenMod 12 nightlies now available for 31 devices, based on Android 5.0.1 Lollipop (LRX22C). LG Optimus One is out of the list to be sure
http://blog.gsmarena.com/cyanogenmo...able-31-devices-based-android-5-0-1-lollipop/
While in other hand, our devs are working to port experimentally newer version of CM12 (Android 5.0.2 LRX22G) on armv6 obsolete devices, though! :good:
You can look at development of android_art as it progresses here:
http://review.androidarmv6.org/#/q/status:merged
and here:
http://review.androidarmv6.org/#/c/7676/
Who dares (try this on p500) win!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1308/
http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150108-EXPERIMENTAL-p500.zip
Sent from my HM 1SW using XDA Free mobile app
xu3sno said:
Who dares (try this on p500) win!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1308/
http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150108-EXPERIMENTAL-p500.zip
Sent from my HM 1SW using XDA Free mobile app
Click to expand...
Click to collapse
Trimmed>>Flashed>>Stuck at CM bootlogo
CCXAlex said:
Trimmed>>Flashed>>Stuck at CM bootlogo
Click to expand...
Click to collapse
+1K
GERRIT_CHANGES: 7676 7748 7693 7651 7751 7792
Code:
7676: * runtime : make entrypoints ARM; if the target arch is lower than
armv7, set armv6.
* compiler: add a new define: ARM_MODE_WORKAROUND, enable it if
the target cpu is arm11. Use ARM assembler and replace
Thumb{1-2} opcodes with ARM ones. Update some code to
support new opcodes
NOTE: kArm is not implemented, probably it use to work only in
portable mode.
7748: Compatibility work around for bad graphics driver dependency
7693: legacy OMX: squashed commit for legacy OMX support for LP
7651: Revert "Revert "Turn on BLE, GATT, and SMP of Bluetooth stack""
7751: msm7x27-common: Initial cm-12 bringup
7792: jemalloc: Force gcc for atomic functions
GCC built-in functions provide advanced things like prefetch, expected, synchronization...
Bootloog attached.
It seems bootloop's culprit is regarding with dynamic shared libraries (lib*.so) which must be fixed first.
It does not work on any device arvm6.
Link
A reminder: unannounced experimental builds that you may see on Jenkins are made by and for developers alone, and are definitely not suitable to be flashed by users. The cm12 totoro build from today doesn't install or boot, and I expect many future builds will be the same, so don't waste your time with it.
Also, a reminder of some things you shouldn't do (now or ever): don't ask for ETAs, don't spam the dev thread, and don't PM me asking for information that isn't on a public post.
There are many things that need to be fixed for armv6 devices. I've sorted out the major issues specific to Broadcom hardware, but there are more important issues that need solving for ARMv6 devices in general that are being working on by several people (assembly errors, ART compatibility, build system integration, etc.). It's going to take time. Thanks for your understanding.
Click to expand...
Click to collapse
Build cm_p500-userdebug-cm-12.0 (Jan 11, 2015 9:45:30 PM)
Androidmeda built it for testing via Jenkins, if you dare to waste your time!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1311/
ROM: http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150111-EXPERIMENTAL-p500.zip
xu3sno said:
Build cm_p500-userdebug-cm-12.0 (Jan 11, 2015 9:45:30 PM)
Androidmeda built it for testing via Jenkins, if you dare to waste your time!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1311/
ROM: http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150111-EXPERIMENTAL-p500.zip
Click to expand...
Click to collapse
If it works on s5360 it will also work on the P500. But this time it does not work perfectly on any device armv6. I will follow up if it worked on my s5360 will report over here.
Thanks for the update by @xu3sno
Any PlayStore said:
If it works on s5360 it will also work on the P500. But this time it does not work perfectly on any device armv6. I will follow up if it worked on my s5360 will report over here.
Thanks for the update by @xu3sno
Click to expand...
Click to collapse
@Any PlayStore
also @CCXAlex (may be you have luck to try it, but I doubt )
Even Any PlayStore has quoted previously, just to satisfy my curiosity, insisted to install cm12-20150111_EXPERIMENTAL-p500.
Trimmed > clean installed > rebooted > boot loop As previous attempt, it seems lib*.so need to be fixed (?)
Don't know it's wasting my time or not
Quote:
A reminder: unannounced experimental builds that you may see on Jenkins are made by and for developers alone, and are definitely not suitable to be flashed by users. The cm12 totoro build from today doesn't install or boot, and I expect many future builds will be the same, so don't waste your time with it.
Click to expand...
Click to collapse
Yes, yes, we know or should know. But, hey, who does not want to be the first to see this play? The only reason I am staying off is because of the CM tricks with switching system and data partitions meaning recoveries are not compatible.
Anyway, diehards within the CM universe, once in that bootloop if ART had indeed done its thing, check remaining system space and contents of those /system/app/... folders. My (un-) educated guess is that this may become the big problem.
xu3sno said:
@Any PlayStore
also @CCXAlex (may be you have luck to try it, but I doubt )
Even Any PlayStore has quoted previously, just to satisfy my curiosity, insisted to install cm12-20150111_EXPERIMENTAL-p500.
Trimmed > clean installed > rebooted > boot loop As previous attempt, it seems lib*.so need to be fixed (?)
Don't know it's wasting my time or not
Click to expand...
Click to collapse
I also attempted to install this. Initially my trimming method seems to have broken update binary, so flash failed. Next installed full ROM (/system =189MB) using @HardLight twrp 2.7.0.0 TLS (successfully flashed). Stuck at boot animation. No log (flashing while driving).
sent from my towelrooted LG L34C using tapatalk
Since this thread is no longer just about me trying to get lollipop running on this phone (I AM still doing that though) I decided to 'rebrand' it as a general development thread for OSA. What's OSA? It stands for Only Some Android...ok so whats that? A team name I came up with to make myself feel more important (btw we're always looking for contributors).
So instead of focusing on just lollipop I will be discussing pretty much anything and everything I am doing in regards to the Desire 510.
Original Post Below:
Hi all, I am currently working on getting lollipop working on the Desire 510. So far I had a successful compile of LiquidSmooth 5.1.1 a couple nights ago but not a successful boot. I am currently 97% done syncing the CyanogenMod 12.1 sources (5.1.1 r3) and am now using the omni twrp sources to ensure a higher compatibility for the recovery, I am hoping for a successful boot soon.
I have the virgin mobile cdma model of the device and that's what I will be targeting although I will do my best to make sure the device tree is universal. If anyone has any insight or advice I am all ears.
I am going to use this thread as a development thread until I get the required 10 posts and I get a booting rom.
OnlySomeDood said:
Hi all, I am currently working on getting lollipop working on the Desire 510. So far I had a successful compile of LiquidSmooth 5.1.1 a couple nights ago but not a successful boot. I am currently 97% done syncing the CyanogenMod 12.1 sources (5.1.1 r3) and am now using the omni twrp sources to ensure a higher compatibility for the recovery, I am hoping for a successful boot soon.
I have the virgin mobile cdma model of the device and that's what I will be targeting although I will do my best to make sure the device tree is universal. If anyone has any insight or advice I am all ears.
I am going to use this thread as a development thread until I get the required 10 posts and I get a booting rom.
Click to expand...
Click to collapse
im pretty sure shinrus device tree has a unified irl,its here https://github.com/shinru2004/android_device_htc_a11 ,also,did you update the kernel you were using? our kernel doesnt have support for loli,all tho rbhero has a branch in his kernel tree that he said works on loli
pattyboi:) said:
im pretty sure shinrus device tree has a unified irl,its here https://github.com/shinru2004/android_device_htc_a11 ,also,did you update the kernel you were using? our kernel doesnt have support for loli,all tho rbhero has a branch in his kernel tree that he said works on loli
Click to expand...
Click to collapse
Im working on all that, I'm looking into using the msm8974 kernel, from what I have read it's practically identical to the 8226, I am also using the a5 (desire 816) as a template since the two devices are so similar. Little by little I am getting there, having to figure out these errors as they come.
OnlySomeDood said:
Im working on all that, I'm looking into using the msm8974 kernel, from what I have read it's practically identical to the 8226, I am also using the a5 (desire 816) as a template since the two devices are so similar. Little by little I am getting there, having to figure out these errors as they come.
Click to expand...
Click to collapse
rbhero has a modded a5 tree up if you wanna take a look at it,and just since your here..
have you gotten a error to something along the lines of:
make: *** No rule to make target `/home/pattyboi/source/out/target/product/a11/obj/SHARED_LIBRARIES/libqdutils_intermediates/export_includes', needed by `/home/pattyboi/source/out/target/product/a11/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/import_includes'. Stop
pattyboi:) said:
rbhero has a modded a5 tree up if you wanna take a look at it,and just since your here..
have you gotten a error to something along the lines of:
make: *** No rule to make target `/home/pattyboi/source/out/target/product/a11/obj/SHARED_LIBRARIES/libqdutils_intermediates/export_includes', needed by `/home/pattyboi/source/out/target/product/a11/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/import_includes'. Stop
Click to expand...
Click to collapse
I actually just did, thanks for the heads up. I am going to look at / try his configs and see where it goes.
Yeah I have gotten a few of those errors, but not on surfaceflinger, mine are mostly on bionic and libcutils
OnlySomeDood said:
I actually just did, thanks for the heads up. I am going to look at / try his configs and see where it goes.
Click to expand...
Click to collapse
gonna be trying that myself,let me know if you get anywhere
for sure, that's what this thread is for afterall
OnlySomeDood said:
for sure, that's what this thread is for afterall
Click to expand...
Click to collapse
You might wanna PM a mod and ask them to move this over to the development area: Desire 510 Android Development.
dip_spit said:
You might wanna PM a mod and ask them to move this over to the development area: Desire 510 Android Development.
Click to expand...
Click to collapse
Well the reason I posted this here is because I don't have the required ten posts yet. So I wouldn't have been able to make this thread to post anything. This is #9 and I am making progress so i will go ahead and contact a mod soon to have it moved over.
OnlySomeDood said:
Well the reason I posted this here is because I don't have the required ten posts yet. So I wouldn't have been able to make this thread to post anything. This is #9 and I am making progress so i will go ahead and contact a mod soon to have it moved over.
Click to expand...
Click to collapse
Gotcha. I didn't even know that was a rule. I was just giving you the heads up lol.
no worries. yeah you need 10 posts in order to post anything in the development subforums for the devices.
I just pm'd a mod and asked to have the thread moved to the appropriate subforum. Also I am making a LITTLE Progress, it does feel like two steps forward and one step back however. I'm confident that between those of us who are wanting it that it will happen.
Not sure if anyone is interested but I created another slack room under my account if anyone developing for the 510 wants to join and collaborate in order to (hopefully) let this device see its potential. Just pm me and i'll send you an invite.
Quickie update, I keep running in to the same set of errors and I know the answer is right in front of my face but im just not seeing it. I have a sneaking suspicion that I may be missing some headers and libraries on my machine but I can't be sure.
Also I've forgotten how much I dislike working with kernels lol
OnlySomeDood said:
no worries. yeah you need 10 posts in order to post anything in the development subforums for the devices.
I just pm'd a mod and asked to have the thread moved to the appropriate subforum. Also I am making a LITTLE Progress, it does feel like two steps forward and one step back however. I'm confident that between those of us who are wanting it that it will happen.
Not sure if anyone is interested but I created another slack room under my account if anyone developing for the 510 wants to join and collaborate in order to (hopefully) let this device see its potential. Just pm me and i'll send you an invite.
Quickie update, I keep running in to the same set of errors and I know the answer is right in front of my face but im just not seeing it. I have a sneaking suspicion that I may be missing some headers and libraries on my machine but I can't be sure.
Also I've forgotten how much I dislike working with kernels lol
Click to expand...
Click to collapse
whats up with the kernel? im good in that department for the most part,roms are...eh,not my specialty
I can't get any kernel to compile, I keep getting failures while making the drivers.
Currently using a pre compiled image to at least try to get the rom built, I can solve these errors, i've done it before on other devices. How's progress on your end if any?
OnlySomeDood said:
I can't get any kernel to compile, I keep getting failures while making the drivers.
Currently using a pre compiled image to at least try to get the rom built, I can solve these errors, i've done it before on other devices. How's progress on your end if any?
Click to expand...
Click to collapse
can you post one of the errors when you get a sec?
& none,got so angry at the stupid libqdutils thing i had last night i havent even attempted anything yet,been working on setting zswap/vnswap up so we have some leeway when it comes to ram..you got github at all?
I was fighting with libcutils for about two days, stupid friggin unicode strings....but I got past that, right now it's mostly "no rule to make target" stuff which is easy enough after you go digging around to find the right file/line to edit. Right this very second though I am working on getting the mkbootimg.mk properly set up and get a recovery image cooked.
OnlySomeDood said:
I was fighting with libcutils for about two days, stupid friggin unicode strings....but I got past that, right now it's mostly "no rule to make target" stuff which is easy enough after you go digging around to find the right file/line to edit. Right this very second though I am working on getting the mkbootimg.mk properly set up and get a recovery image cooked.
Click to expand...
Click to collapse
i think rbheros last twrp works with loli,never tested it,all tho he should me screenshots of him running it,so you might just wanna save the time and use it
pattyboi:) said:
i think rbheros last twrp works with loli,never tested it,all tho he should me screenshots of him running it,so you might just wanna save the time and use it
Click to expand...
Click to collapse
The TeamYAR TWRP doesn't, not to my knowledge. He had one built locally but he didn't send it to me. I have a CM12 kernel that he built that boots (rom is still ****) but needs default encryption disabled amongst other things.
dip_spit said:
The TeamYAR TWRP doesn't, not to my knowledge. He had one built locally but he didn't send it to me. I have a CM12 kernel that he built that boots (rom is still ****) but needs default encryption disabled amongst other things.
Click to expand...
Click to collapse
well sh*t..i think there is a way to disable encryption from the ramdisk..not entirely sure how tho
pattyboi:) said:
i think rbheros last twrp works with loli,never tested it,all tho he should me screenshots of him running it,so you might just wanna save the time and use it
Click to expand...
Click to collapse
It's kind of a "me" thing, If I am going to go thru the effort to port cyanogenmod to an unsupported device then I'll take the extra time to compile every bit, including the recovery.
OnlySomeDood said:
It's kind of a "me" thing, If I am going to go thru the effort to port cyanogenmod to an unsupported device then I'll take the extra time to compile every bit, including the recovery.
Click to expand...
Click to collapse
i dont blame you,makes sense to me
Discontinued.
Awaiting for thread deletion.
Thanks...Nice work after your miui 5 ROM
Help please..
Need someone who can risk his device by testing this ROM......
Happy holi.....
Happy holi my friends...
May this holi bring lots of Colors in your life!! and in mine too.
Kunal Gautam said:
Need someone who can risk his device by testing this ROM......
Click to expand...
Click to collapse
I tried to install but it gives error 7 i think update.script should be rechecked.
Deep_dhimaan said:
I tried to install but it gives error 7 i think update.script should be rechecked.
Click to expand...
Click to collapse
Thank you very much, i've understood whats the problem( as a pm by ashkineeeeee).
New update coming soon. Stay tuned.
Hey bros...
so there were some problem with permissions, it seems that it is fixed now..
Flash the ROM and review here....
----------------------edit 1---------------------
dont flash the rom now!!!
Some files are missing in boot.img
how stupid i am!!
------------------------edit 2-----------------------
Flash it now!
Last build not installed,error 7.
mels01 said:
Last build not installed,error 7.
Click to expand...
Click to collapse
Logs,screenshots?
Try installing from internal storage... Or update your recovery to the latest one by android andi...
Thanks!
Hey, I would like to help out, can I have the link to the ROM?
theportal2 said:
Hey, I would like to help out, can I have the link to the ROM?
Click to expand...
Click to collapse
I agree this message is a bit long but it is worth reading.
- Thanks, but sorry. Even if I give you the links and even if spend your precious time you would only be able to fix the error 7.
- Actually I've already fixed that(or know what's the issue atleast). There are files that are missing from the directories that are listed in the updater script. They cannot be deleted as the original base ROM I compiled was from UA(unlegacy android) that are based on the newer sources.
- Some files that are required for MIUI are also missing.
- Boot.img is incomplete. Which will result in bootloop even if I upload the error 7 fixed ROM.
- I am giving my board exams that are one of the biggest exams in India. And I cannot afford to score less in these.
- All I need is a older base ROM ,CyanogenMod 11 made around may of 2016. And also it must support init.d because the port ROM requires that.
- I've taken permissions from the maker of the port ROM. He has allowed me to proceed.
- All I need is permission from Android-Andi, as only he has older CM ROMs.
- I cannot compile because older sources are not available or maybe I am not known to them
Hope you understand. Thank you.
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam
Links
Kunal Gautam said:
I agree this message is a bit long but it is worth reading.
- Thanks, but sorry. Even if I give you the links and even if spend your precious time you would only be able to fix the error 7.
- Actually I've already fixed that(or know what's the issue atleast). There are files that are missing from the directories that are listed in the updater script. They cannot be deleted as the original base ROM I compiled was from UA(unlegacy android) that are based on the newer sources.
- Some files that are required for MIUI are also missing.
- Boot.img is incomplete. Which will result in bootloop even if I upload the error 7 fixed ROM.
- I am giving my board exams that are one of the biggest exams in India. And I cannot afford to score less in these.
- All I need is a older base ROM ,CyanogenMod 11 made around may of 2016. And also it must support init.d because the port ROM requires that.
- I've taken permissions from the maker of the port ROM. He has allowed me to proceed.
- All I need is permission from Android-Andi, as only he has older CM ROMs.
- I cannot compile because older sources are not available or maybe I am not known to them
Hope you understand. Thank you.
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam
Click to expand...
Click to collapse
Have you seen this CM 11? https://forum.xda-developers.com/galaxy-tab-2/7-inch-development/rom-cm-11-0-galaxy-tab-2-t3737392
Just made last month by @Deltadroid
Links are removed because *the ROM is not complete yet*.
Thanks, but I need to confirm a few things before I could use a ROM(includes init.d support and a bunch of other things). Also, it is very important that deltadroid provide me permission to use his ROM.
Thank you!
Regards,
KG
-----_edit_--------
I just saw deltadroid's thread, the title clearly says that the ROM is for p3110. I want to make a unified one. I need a ROM made with unified device tree.
If I do port, it will only work on p3110 and maybe on every 7" device. I don't want do this.
Sorry, but yeah thanks!
Just wait till 3 april 2018. Most probably I will upload.
Edit 2
Or I must say it an update. 75 percent of the work is done. Somehow I managed to get a base ROM(only I know how). Only build.prop editing and Updater script editing work left(these are the most difficult BTW).
Update coming soon. Stay tuned.
I've updated the links. I've uploaded the new ROM. I've done with porting(i guess). I've used a lot of time.
Flash and review!
Kunal Gautam said:
I've updated the links. I've uploaded the new ROM. I've done with porting(i guess). I've used a lot of time.
Flash and review!
Click to expand...
Click to collapse
No wonder the ROM doesn't work.... Security patch is in a wrong format.
"ro.build.version.security_patch=2080-17-March"
It should be, "ro.build.version.security_patch=2018-03-01"
or,
"ro.build.version.security_patch=2018-03-05"
And this, hardly doubt this will work, but idk.
"ro.build.date.utc=999999999999"
Mistakes....................
EDIT**** Build id should be the app id: example lets say the id is 678, on build.prop, it would say 678.
you have, "ro.build.id=KUNAL"
secretwolf98 said:
No wonder the ROM doesn't work.... Security patch is in a wrong format.
"ro.build.version.security_patch=2080-17-March"
It should be, "ro.build.version.security_patch=2018-03-01"
or,
"ro.build.version.security_patch=2018-03-05"
And this, hardly doubt this will work, but idk.
"ro.build.date.utc=999999999999"
Mistakes....................
EDIT**** Build id should be the app id: example lets say the id is 678, on build.prop, it would say 678.
you have, "ro.build.id=KUNAL"
Click to expand...
Click to collapse
You, sir, definitely have a lot to offer. I am afraid that this is not the actual problem. By now, I surely understand the importance of logs. Would be very helpful if someone could arrange me them.
And about your post it seemed really rude, raw, insulting and manipulating to me. But however, helpful. It makes it really hard to continue developing for a 6 years old Tab, with hardware that has nothing to offer in 2018. At least, I am trying.
Since, this was an Alpha build(because I moved sources) these problems are sure to arise. I did the same(build.prop things) with my kinda successful ROM MIUI 5(see it in the 7" forums).
I guess you haven't tasted port ROMs yet. They are hard to build. Alike your compiling ones, you have source, type some commands, turn your computer on for about 5 hours, when done upload it.
I am sure you must have did trail and error (in chemistry and math) porting ROMs is just the same. I am sure, that as a developer, you must know what logs actually mean.
But whatever, thank you for you review(insult I guess).
Kunal Gautam said:
You, sir, definitely have a lot to offer. I am afraid that this is not the actual problem. By now, I surely understand the importance of logs. Would be very helpful if someone could arrange me them.
And about your post it seemed really rude, raw, insulting and manipulating to me. But however, helpful. It makes it really hard to continue developing for a 6 years old Tab, with hardware that has nothing to offer in 2018. At least, I am trying.
Since, this was an Alpha build(because I moved sources) these problems are sure to arise. I did the same(build.prop things) with my kinda successful ROM MIUI 5(see it in the 7" forums).
I guess you haven't tasted port ROMs yet. They are hard to build. Alike your compiling ones, you have source, type some commands, turn your computer on for about 5 hours, when done upload it.
I am sure you must have did trail and error (in chemistry and math) porting ROMs is just the same. I am sure, that as a developer, you must know what logs actually mean.
But whatever, thank you for you review(insult I guess).
Click to expand...
Click to collapse
FYI, I port ROMs. It was pointers what to fix, if you wanted to get this ROM better, than it is already.
Kunal Gautam said:
(...)
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam
Click to expand...
Click to collapse
Sorry, I won't give permissions after different people used my ROMs as base in the past without permissions. Hope there is a learning affect....
Since i love OpenSource: Sources are available on every official GitHub (slim, Omni, Lineage, UA) and up to date (note: I wouldn't have to do this, I could keep all device trees private but I am updating them for everyone - always). You'll have to compile your own base ROM to use for such port ROMs (I am not a fan of).
Android-Andi said:
Sorry, I won't give permissions after different people used my ROMs as base in the past without permissions. Hope there is a learning affect....
Since i love OpenSource: Sources are available on every official GitHub (slim, Omni, Lineage, UA) and up to date (note: I wouldn't have to do this, I could keep all device trees private but I am updating them for everyone - always). You'll have to compile your own base ROM to use for such port ROMs (I am not a fan of).
Click to expand...
Click to collapse
Thank you. For at least replying. You works will always be appreciated. Now, I am gonna close this thread. Thanks again!