I’ll start by admiting that, in the arts of cooking/building/porting android innards, I’m closer to being a complete noob than na intermediate user.
I own a Newman K1S, JB 4.2.2, MT6592, 2Gb/16Gb, 720p, and, sadly for me, it looks like the manufacturer (Newman Mobile, or Newsmy, who knows) pretty much disavows any knowledge of this model ever being built or sold. No reference to it, no community, no android updates or ROM releases.
Taking into account some MediaTek source codes for KitKat were made available earlier this year (even if unofficially), I was wondering:
So, question number 1 – Is it possible to build android 4.4 for my device straight from said sources? Or are they unreliable and it would be best not to attempt it?
And question number 2 – Being at the noob level, should I stay away from such a task? And, in this case, would I be better off porting a 4.4 ROM from a similar spec’ed device?
Also, while browsing needrom, I noticed that a 4.4 “official” ROM was posted for my device. However, having flashed it, I found that it produces no sounds from the external speaker (although with headphones it works fine). Same thing was experienced by other users, and there is no fix so far.
Which takes me to question number 3 – What may I try, in order to fix an issue like this? Does KK use the same sound drivers as JB, and maybe it’s only a matter of replacing them? (if so, I believe this is within my grasp, even if I must unpack the IMG files to reach the drivers)
Lastly, Newman K1S has a severe overheating problem when pushed, which I believe would be easily solved by underclocking it to 1.3 or 1.5, or maybe implementing an optimized kernel.
Final question – How do I manage to underclock with my current kernel, or, better yet, how do I port a custom, optimized kernel to my device?
Congratulations to everyone who managed to read this far, and thank you in advance for any help provided. I’ve spent the last few days reading tutorials and guides, only to become even more confused… I did manage to get android kitchen running on my Windows laptop, though!
Links to recent/updated guides that might be useful are appreciated, too.
Edit: I was told to ask this in this section of the forum so here goes.
Hi,
some time ago i bought a 50€ chinese tablet to mess with. It has android v4.0.4 on it and is very slow/ has a lot of useless stuff. In my attempt to educate myself on Android OS, I'm trying to build my own custom rom for it using this thread: http://forum.xda-developers.com/showthread.php?t=1801690
I'm at the point where I could repack my work and flash it to this tablet, but all i've achieved so far is simplified version (less random apps and few tweaks here and there) of existing rom.
I want to update this tablet's android version but I'm completely unsure how I'm supposed to do that and google isn't being of any help as the search results are just bunch of those irritating blog posts that in nutshell just explain how to plug your usb cable into your pc.
No updates are provided by the manufacturer himself (duh).
Do I have to get desired android version's source code and integrate it with existing files or something?
Any help is appreciated.
Dear xda community,
I just made my account so I can ask the question written above (and join your community :fingers-crossed. I don't ask for instructions, guides etc. I just want to know if it's possible and if so, how hard is it?
There was a guy who always ported the MIUI official global developer SD roms to the MTK phones. It worked pretty well, though I'm not a great fan of MIUI's design & bloatware. Long story short: he did it in a very short period of time.
There are many Android 5 (6 at best) custom roms out there, though we have Android 7 (offical resurrection remix OS) for the SD device. MTK and Snapdragon share the latest MIUI/Android version (7.11.23), so maybe copy/paste files is possible until a certain limit?
Thanks for your answers and best regards (and sorry if I'm not seeing any obvious mistake, I'm just learning C++ at the moment and that's all )
Marvin M.
MarvinMe said:
Dear xda community,
I just made my account so I can ask the question written above (and join your community :fingers-crossed. I don't ask for instructions, guides etc. I just want to know if it's possible and if so, how hard is it?
There was a guy who always ported the MIUI official global developer SD roms to the MTK phones. It worked pretty well, though I'm not a great fan of MIUI's design & bloatware. Long story short: he did it in a very short period of time.
There are many Android 5 (6 at best) custom roms out there, though we have Android 7 (offical resurrection remix OS) for the SD device. MTK and Snapdragon share the latest MIUI/Android version (7.11.23), so maybe copy/paste files is possible until a certain limit?
Thanks for your answers and best regards (and sorry if I'm not seeing any obvious mistake, I'm just learning C++ at the moment and that's all )
Marvin M.
Click to expand...
Click to collapse
Actually No... SD and MTK are 2 different architectures and the kernel having the apis implementated wont be common... But it would be little simpler if porting rom also shares the same archecture... So u need to browse similar roms which are in same architecture....
Also to port across different OS versions, you need kernel source to provide respective drivers.... Hope it helps
Hello everyone.
I'm a more-or-less experienced desktop developer (currently PHD student - mainly I develop desktop apps for social sciences research) and sadly an absolute amateur in Android development. To the topic though:
- I need a safe and amateur friendly way to root my Tablet: Huawei Mediapad M3 LTE version, 32GB, currently with Android 6 (for some reason Huawei says Android 7 should already be there yet it ain't available for me). What I need this root for is just one thing: Linux Deploy. I need to be able to work on-the-go and having access to my linux apps is gravely required to do so (mainly Atom for general coding, R for statistics, Pycharm + IntelliJ or Eclipse for my actual development job and several others as I currently started learning JS too).
- I do NOT need to flash custom ROM's (I'm fine with my Android 6 as it is). I only need Linux Deploy and being able to grant some apps SU privilege.
Reading around those forums I found several "solutions" to root my device but as it is my first rodeo I'm still kinda scared of loosing my fresh acquisition to my own incompetence. What I found are:
- KingRoot/KingoRoot - both seem to be heavily accused of stealing personal data, and as I move around with research data of my own and from other scientists it seems like a no-go for me.
- Multi-stage Bootload, TWRP, SRK rooting which scares the hell out of me at how complicated and error-friendly it is.
https://forum.xda-developers.com/mediapad-m3/how-to/root-success-t3489547
- Some flashing tools from here, which mostly are directed at flashing ROMS.
https://www.xda-developers.com/root/
- And awesome CF-Auto-Root that looked like a perfect thing just made for me, until I realized it's for Samsung devices only.
Getting to my question/request now: Can someone either confirm rooting EXACTLY my model of a tablet in a certain way or just guide me through the process in less erratic way than this topic:
https://forum.xda-developers.com/mediapad-m3/how-to/root-success-t3489547
...which is linking to several other topics which in turns are linking to several other pages, which in the end is about as clear/understandable as a muddy river and as well organized as my life lately (hint: it's NOT organized).
Thanks in advance to anyone willing to step up and help
Best Regards
Nec
INTRODUCTION
Have you ever dreamed to get not any device but YOURS on the wide screen of your computer? Create a custom ROM and emulate it, or just check another custom ROM compatibility virtually without having to flash and risk your everyday tool? Well I did and I still do!
In the old times this was possible but, unfortunately, it's no longer the case. Since our beloved mobile devices got more features, system has become also more complex. This is why we can't run a custom ROM only with system and data images as before anymore. Unless you still want to develop on Gingerbread and below — seriously? — we need to move to another solution.
And this is what this project is for!
According to the fact that we're not all pro developers and / or we're not all rich enough to buy multiple devices in case of brick, I think such project is necessary to avoid taking stupid risks like we do now.
ORGANIZATION
Currently the project is committed under the name of "AndROMega".
It is planned to work under the Windows and Linux environments. An eventual port for Mac OS isn't envisaged for now but still welcome if someone wish to work on once a version is released.
By the way, this project being free and open-source, everybody can join, improve it but thieving (including copying then claiming project as-is / unmodified is your and, worse, selling this common work) is absolutely UNALLOWED. This must still free, open-source and mention the original authors (me and other devs eventually joining) in case of copying to make custom release. All of this juridical stuff will be put in a license file as usual anyway.
The QEMU emulating software will be used to facilitate the cross-platforming of the project software. It is fast, powerful, reliable, and, moreover: FREE.
Edit: Great new! Editing a custom Android emulator from scratch won't be in the question anymore!
A Github repo has been created allowing to run a stock AOSP Android ROM, so one step is made
Link to this repo: https://github.com/aosp-mirror/platform_external_qemu
Other notes coming soon in this thread...
Reserved.
Atronid said:
INTRODUCTION
Have you ever dreamed to get not any device but YOUR on the wide screen of your computer? Create custom ROM and emulate it or just check another custom ROM compatibility virtually without having to flash and risk your everyday tool? Well I did and I still do!
In the old times this was possible but, unfortunately, it's no longer the case. Since our beloved mobile devices got more features, system became also more complex. This is why we can't run a custom ROM only with system and data images as before anymore. Unless you still want to develop on Gingerbread and below — seriously? — we need to move to another solution.
And this is what this project is for!
According to the fact that we're not all pro developers and / or we're not all rich enough to buy multiple devices in case of brick, I think such project is necessary to avoid taking stupid risks as we do for now.
ORGANIZATION
Currently the project is committed under the name of "AndROMega".
It is planned to work under the Windows and Linux environment. An eventual port for Mac OS isn't envisaged for now but still welcome if somebody wish to work on once a version is released.
By the way, this project being free and open-source, everybody can join, improve it but thieving (including copying then claiming project as-is / unmodified is your and, worse, selling this common work) is absolutely UNALLOWED. This must still free, open-source and mention the original authors (me and other devs eventually joining) in case of copying to make custom release. All of this juridical stuff will be put in a license file as usual anyway.
The QEMU emulating software will be used to facilitate the cross-platforming of the project software. It is fast, powerful, reliable, and, moreover: FREE.
Edit: Great new! Editing a custom Android emulator from scratch won't be in the question anymore!
A Github repo has been created allowing to run a stock AOSP Android ROM, so one step is made
Link to this repo: https://github.com/aosp-mirror/platform_external_qemu
Other notes coming soon in this thread...
Click to expand...
Click to collapse
So what do you mean by custom rom environment builder? Do you mean when you port a rom and it has glitches and the environment fixes it or what? I'd be happy to help with this.
NonStickAtom785 said:
So what do you mean by custom rom environment builder? Do you mean when you port a rom and it has glitches and the environment fixes it or what? I'd be happy to help with this.
Click to expand...
Click to collapse
I don't really understand your question, but I'll sum up what the project is, hoping it will help you understand.
It's nothing more or less than a tool that mimic hardware and specific components and architecture of a phone model. It is supposed to be more than an AVD, allowing you to literally flash a custom ROM and debug it virtually instead of having to buy the phone, flash it, screw everything if something goes wrong, restore backup, etc.
Back when I got this idea (before it got forgotten among the million projects I have) I thought the hardest part was to get the core component of every phone (ramdisk, ROM, bootloader — assuming it's possible, otherwise "create" a replicant) and get the hardware spec mimicked with QEMU. Now I grew a bit and got a new-featured phone (seamless partition system that was pretty new to me), I know it will be even more complicated.
Since I'm not really available this year because of my exams, this project will still idle for a while. But I won't abandon it, so if the principle interest you and you're ready to give a hand you are welcome !
I'm In!
Atronid said:
I don't really understand your question, but I'll sum up what the project is, hoping it will help you understand.
It's nothing more or less than a tool that mimic hardware and specific components and architecture of a phone model. It is supposed to be more than an AVD, allowing you to literally flash a custom ROM and debug it virtually instead of having to buy the phone, flash it, screw everything if something goes wrong, restore backup, etc.
Back when I got this idea (before it got forgotten among the million projects I have) I thought the hardest part was to get the core component of every phone (ramdisk, ROM, bootloader — assuming it's possible, otherwise "create" a replicant) and get the hardware spec mimicked with QEMU. Now I grew a bit and got a new-featured phone (seamless partition system that was pretty new to me), I know it will be even more complicated.
Since I'm not really available this year because of my exams, this project will still idle for a while. But I won't abandon it, so if the principle interest you and you're ready to give a hand you are welcome !
Click to expand...
Click to collapse
Well this is a very interesting idea. It would be very useful for the rooted phones that don't have any custom roms already built.
Maybe you wouldn't have to get the core components of every phone all at once. Maybe it you could make the program to extract a twrp or cwm backup, and have a database of all the ramdisks and chipsets that the program will have access to.
I think this project is very useful and I would like to start in the development of it or aid you in it. PM me with more details :good:.
NonStickAtom785 said:
Well this is a very interesting idea. It would be very useful for the rooted phones that don't have any custom roms already built.
Maybe you wouldn't have to get the core components of every phone all at once. Maybe it you could make the program to extract a twrp or cwm backup, and have a database of all the ramdisks and chipsets that the program will have access to.
I think this project is very useful and I would like to start in the development of it or aid you in it. PM me with more details :good:.
Click to expand...
Click to collapse
Yes, backup extraction and component database was the original idea
Thank you for your help! I'll PM you as soon as the project starts :fingers-crossed:
Atronid said:
Yes, backup extraction and component database was the original idea
Thank you for your help! I'll PM you as soon as the project starts :fingers-crossed:
Click to expand...
Click to collapse
Thanks:laugh:
Best thing ever, life saver etc, I am ready to do whatever you want just this thing to succeed!
ender1324 said:
Best thing ever, life saver etc, I am ready to do whatever you want just this thing to succeed!
Click to expand...
Click to collapse
That's very nice, thanks!
As mentionned earlier, the project won't start right now due to my work, but in theory I should be available and ready to start it in the next months! I'll DM you as soon as it gets its first kick !