Database Users

Roms and Kernels

Sorry for noob question (and PLEASE DONT FLAME ME BECAUSE OF THIS) but will roms/kernels for other devices work with the incredible? just wondering\
AND PLEASE, IF YOU THINK I AM A COMPLETE IDIOT FOR POSTING THIS THEN JUST KEEP IT TO YOURSELF

pretty sure they won't or people would be posting about which ones worked well and which ones didnt.
i think a rom has to have a certain amount of customization for the actual device it is going to be loaded on before it will work.

JustinD2473 said:
pretty sure they won't or people would be posting about which ones worked well and which ones didnt.
i think a rom has to have a certain amount of customization for the actual device it is going to be loaded on before it will work.
Click to expand...
Click to collapse
Thank you

How is your froyo port going to work if you didn't know this? Just wondering.
Sent from my ADR6300 using XDA App

grape ape---i did know, just confirmiing

rr12106 said:
will roms/kernels for other devices work with the incredible? just wondering
Click to expand...
Click to collapse
No, if you try to flash a rom or kernel made for another device you can brick your phone.

Captchunk said:
No, if you try to flash a rom or kernel made for another device you can brick your phone.
Click to expand...
Click to collapse
Or get stuck in boot loops

TNS201 said:
Or get stuck in boot loops
Click to expand...
Click to collapse
or explode in a ball of flame...
oh wait... that was mixing gasoline with new roms... and fire...
But yea, should probably avoid flashing roms for other devices without properly porting them.

Never flash a ROM that was meant for another device. You risk not being able to use the phone again.
And if anyone were to flame you for posting this questions they'd take a lot of crap from a lot of people for being a douche.
Don't ever be afraid to post a question

hexto said:
And if anyone were to flame you for posting this questions they'd take a lot of crap from a lot of people for being a douche.
Click to expand...
Click to collapse
Usually this is true, but the OP knew he was risking flame because he's claimed in other threads to be an experienced in building ROMs and knew how to port Froyo to the Incredible.
That doesn't really mesh well with his noob question here.

Reported. This again BELONGS IN GENERAL...man the second post in like 3 hours to be in the wrong section..

elborak said:
Usually this is true, but the OP knew he was risking flame because he's claimed in other threads to be an experienced in building ROMs and knew how to port Froyo to the Incredible.
That doesn't really mesh well with his noob question here.
Click to expand...
Click to collapse
However, he knows, as well as we, that he was over exaggerating on his original claims. We did encourage him to ask questions and learn, can't flame him for making an effort to go down the right path, ask questions, learn, experiment. I'd rather him ask questions, then post falsified claims of froyo builds etc. Much rather.

CaptainTaco said:
We did encourage him to ask questions and learn, can't flame him for making an effort to go down the right path, ask questions, learn, experiment. I'd rather him ask questions, then post falsified claims of froyo builds etc. Much rather.
Click to expand...
Click to collapse
True. Very true.

Thread moved to General.

rr12106 said:
Sorry for noob question (and PLEASE DONT FLAME ME BECAUSE OF THIS) but will roms/kernels for other devices work with the incredible? just wondering\
AND PLEASE, IF YOU THINK I AM A COMPLETE IDIOT FOR POSTING THIS THEN JUST KEEP IT TO YOURSELF
Click to expand...
Click to collapse
I've watched your posts, I know a few folks who are ambitious and think this whole "programming thing" is easy. I'll try to make this simple.
Think of it like this... I compiled an ultra small Kernel of Linux, I only compiled it for a specific computer so I built as much as I could for this specific computer into the kernel, AMD MP, Intel GPU and northbridge, USB 2.0... this way I didn't have to load Modules, it was part of the kernel.
When you install Unix, old school anyway, you are prompted for computer specs so it knows which pre-compiled kernel to select (AMD versus i586 versus i386... etc.) to run the best on your machine. These days it autodetects and makes it easy.
Android is a form of *nix so behaves the same... manufactures compile kernels specific to their devices so that they perform better.
Now, If I used an old Kernel that didn't support USB2 and only supported USB1 then I would be running slow at USB1 or would have to compile without USB at all and load a module that enabled support for USB2...
Android versions are being released with updated kernels for greater support of a wider variety of devices at the kernel level, less modules to load means a faster machine. Some functions still work better with poer saving setups as a module (802.11b/g/n for instance will almost always be a module).
"ROM" which means Read Only Memory are copies of modified kernels from the same device. If I copied the kernel from my machine to another it wouldn't work unless it was identical specs, even one item off and you get kernel dumps, it doesn't know how to talk to your hardware.
Get an idea of what is involved in compiling a kernel here: http://www.linuxforums.org/forum/linux-kernel/55612-mini-howto-compile-linux-kernel-2-6-a.html
I hope this helps you to see that even someone who knows BSD, Linux and Unix... with multiple certifications for Linux (and countless other platforms) and more than 20 years as an engineer... I won't touch making a ROM or trying to modify the bootloader. I wait for the people who know Android's OS, the way it's built, the way it functions... I allow these geniuses to build cool ROMs. I send them donations for their time as some have sent me donations on other forums for my time on other subjects.
It's not as easy as dropping "som 1337 romz" into some folder and presto, "i'z rokn FroYo homz"... it's so much more than that. Someone has to compile the kernel and get the hardware working... it's just easier to wait for the manufacturer to release an update and then find a way to gain root access to do what we want with it.

Additional note:
Check the latest kernel version of Linux here: http://www.kernel.org/
Go into settings and see what version your Doid's Kernel is.
I am going on a limb here but I'm pretty sure there is a correlation.

compnird said:
It's not as easy as dropping "som 1337 romz" into some folder and presto, "i'z rokn FroYo homz"... it's so much more than that.
Click to expand...
Click to collapse
LMAO!! Nice explanation, though.

compnird said:
I've watched your posts, I know a few folks who are ambitious and think this whole "programming thing" is easy. I'll try to make this simple.
Think of it like this... I compiled an ultra small Kernel of Linux, I only compiled it for a specific computer so I built as much as I could for this specific computer into the kernel, AMD MP, Intel GPU and northbridge, USB 2.0... this way I didn't have to load Modules, it was part of the kernel.
When you install Unix, old school anyway, you are prompted for computer specs so it knows which pre-compiled kernel to select (AMD versus i586 versus i386... etc.) to run the best on your machine. These days it autodetects and makes it easy.
Android is a form of *nix so behaves the same... manufactures compile kernels specific to their devices so that they perform better.
Now, If I used an old Kernel that didn't support USB2 and only supported USB1 then I would be running slow at USB1 or would have to compile without USB at all and load a module that enabled support for USB2...
Android versions are being released with updated kernels for greater support of a wider variety of devices at the kernel level, less modules to load means a faster machine. Some functions still work better with poer saving setups as a module (802.11b/g/n for instance will almost always be a module).
"ROM" which means Read Only Memory are copies of modified kernels from the same device. If I copied the kernel from my machine to another it wouldn't work unless it was identical specs, even one item off and you get kernel dumps, it doesn't know how to talk to your hardware.
Get an idea of what is involved in compiling a kernel here: http://www.linuxforums.org/forum/linux-kernel/55612-mini-howto-compile-linux-kernel-2-6-a.html
I hope this helps you to see that even someone who knows BSD, Linux and Unix... with multiple certifications for Linux (and countless other platforms) and more than 20 years as an engineer... I won't touch making a ROM or trying to modify the bootloader. I wait for the people who know Android's OS, the way it's built, the way it functions... I allow these geniuses to build cool ROMs. I send them donations for their time as some have sent me donations on other forums for my time on other subjects.
It's not as easy as dropping "som 1337 romz" into some folder and presto, "i'z rokn FroYo homz"... it's so much more than that. Someone has to compile the kernel and get the hardware working... it's just easier to wait for the manufacturer to release an update and then find a way to gain root access to do what we want with it.
Click to expand...
Click to collapse
Thanks...that helped alot
Sent from my Incredible using XDA App

[Q] What does it take to port new versions of Android to a handset?

I'm hoping somebody will be able to educate me a bit here on some deep technical questions. I've been searching for some information on this topic for a while now but without any luck. In a nutshell what I am curious about is this.. if I were to, lets say, build my own new handset, what would be entailed in getting android to work on it?
I know a kernel must be built with all the drivers and modules to communicate with any specific hardware/radios etc. But once you've got the kernel, is there still more porting that has to be done in the core android code? Are there significant CPU architectural differences or some other major differences between handsets that require more porting within the rest of the OS code? (Side question: if I want to build a kernel from source, what tools do I need)
To ask my question more specifically with the Epic, what is going to be necessary to get Gingerbread on it? If we already have the source for Eclair, or when we get the source for Froyo on the Epic.. what is it that makes it more than just a matter of pulling the drivers from those versions to make things work. Is android not built in a modular enough way to enable that?
I am myself a developer, but as I'm sure is obvious from my questions.. I'm not very experienced at OS level development. And what limited knowledge I do have mainly comes from making correlations to desktop OS, which is probably what is leading me astray.
I'm just really craving to know more about this stuff, so thanks ahead of time to anyone who takes their time to school me and help me understand. If there is any material out there that I should just go RTFM, I'd like to do that but please point me in the right direction.
Thanks!

FYI, your post/s do not pertain to any direct development. They are just generalized questions that can be answered with a simple search.
See Here
Reported as belonging in Q&A/general.

The most difficult part is porting drivers (if they're not already part of the kernel mainline) and device-specific glue code to the new kernel base. This is difficult becuase (i) it's a fair amount of code, (ii) the kernel does not have a stable API, so the necessary changes may be somewhat far reaching, and (iii) bugs that crop up are often more difficult to pin down and fix than in userspace programs. It also doesn't help the matter that Samsung's portion of the kernel code is messy, buggy, and just generally not in a state that would make it easy to port over to a new tree.
The reason why we can't just port Eclair drivers to Froyo, or Froyo drivers to Gingerbread, is that there's a fair number of proprietary modules on the phone (LCD, WiMAX, the entire storage stack, etc.) to which we don't have the source code. These modules are compiled against a specific kernel minor version (e.g., 2.6.29 for Eclair) and won't load in Froyo or Gingerbread. The version number can be faked, but if there's any change in the module API, or in the "API" (which isn't even formally defined) of dependent kernel code, all bets are off.
In theory if there's any Galaxy S device with a Gingerbread release, it might be possible to get a limited-capability kernel up and running, depending on how much the proprietary drivers change across devices (hopefully not much). The Nexus S doesn't count though as Google replaced the entire proprietary flash stoage stack with a GPL-based one. While we might be able to get such running on Galaxy S hardware, it would be incompatible with the existing storage layer and would necessitate a full device flash. Not really something you want to do when an official update with a complete set of drivers is going to be made in the "near" future.
Aside from the kernel, you would have to modify the parts of the Android userland that interface with hardware specific components, for example the "4G" (WiMAX) settings menu and such. I think much of the modem interaction also happens in userland. Then you have to port over whatever custom skin (e.g., TouchWiz) you have.
For some reason this is often believed to be the most difficult and time consuming part of a port, i.e., it's commonly complained that "HTC & Samsung delay releases to port Sense & TouchWiz, if they just dumped them and went AOSP updates would be a lot faster." Honestly it's not. It's an API update like any other Android app, and third party launchers don't seem to have significant problems here.
Mind you, I mention the difficulties of kernel porting without having actually attempted to do it myself, largely becuase it is so daunting. I know there's folks interested in doing this, and perhaps they have some tricks that make it a bit easier in a specific scenario. In general though, these are the difficulties one enounters when trying to port new Linux versions to any embedded platform.

I've often wondered this myself, as well as wondered why Google seemed to get caught with their pants down.
Now granted I don't know the nitty gritty details, but I don't understand why android wasn't written in a manner where as much of it as possible is just apps, and anything that is core is written where the handset makers just need to do the very low level stuff.
On top of that then it could have been made to be more easily themed, even rather dramatically.
Samsung/HTC should only be maintaining the low level "android wants the gps location, I know how to work this specific chip and give it back" and Sense/TouchWiz should just be a theme, and some custom widgets. Android itself should be virtually untouched between those two layers, and updates that don't change how it has to interact with the hardware or the themes should come straight from google.
Thankfully things have at least started to move this way. (you don't need to roll out a ROM update through sprint because Google updated the market like you used to, etc)
If Dell wants to customize Win 7 they add onto it, they don't roll their own copy of it, creating god knows how many fragmentation issues in the meantime. (And yes, I know Windows isn't open source, so they can't, but you get what I'm saying.) Because the second they did that they'd then take on a much larger QA burden, on top of everything else.
If android is untouched for the most part, it works, or it's a bug for everyone. You'd only need to test calls to your low level updates, which could for the most part be automated. The second you start changing a line here and there in the source code, now all of a sudden you have to do the "If I make a calendar item while on a call on a leap year the phone reboots" type QA/Support as well.
Edit: And of course it's very possible that is more or less how it is and the handset makers just flat out take longer to update then anyone imagined they would.

What language/s do you have to know to do all this?

nubsors said:
What language/s do you have to know to do all this?
Click to expand...
Click to collapse
C for kernel and Os. Java for apps(sdk). C and java(ndk/sdk) for apps that require native code implementations of things (eg. The VLC player that is coming. It wasn't possible until the latest edition of the ndk.)
Sent from my SPH-D700 using XDA App

Thank you mkasick for a great detailed answer. I didn't think about the fact there are closed source drivers to worry about as well, and that explains a lot.
@ghostrid3r: I did plenty of simple searches which did not answer my questions before posting, but thank you for the link. Also, not that it matters to me.. but is the development section just for releasing custom roms or something? If questions directly pertaining to development details don't belong there, seems to me the section should be renamed to "Epic 4G Custom Roms" instead.

[CRAZYTHEORY] Joint HC Developement?

Hello there,
I have this theory... I want to hear your opinions to see if I'm just crazy or I'm correct in thinking this.
After seeing how the unmodified Acer Iconia Galaxy ROM + modified ASUS Transformer kernel (Clemsyn's) worked on a Transformer I started to think that this could be because of all the Honeycomb tablets are running a pretty similar OS configuration ("stock-like" Honeycomb).
Am I right in thinking this (I haven't actually used any other HC tablet except the Iconia)?
If this is right, it kind of explains why an unmodified ROM developed for the Iconia works with our device, as they are using pretty similar systems. The main difference, of course, is the hardware. This explains the wifi, battery and other issues in this example. This was partly corrected from the use of an ASUS TF kernel (Clemsyns) with the same ROM since the kernel provides the needed interfaces, modules, whatever for the respective hardware.
Of course, the kernels between the devices, I'm assuming as I haven't actually compared the source, are pretty similar aside from certain hardware modules that have been left out during compilation, as they are both just modified Linux kernel. This explains why the Iconia ROM worked (mostly) even when using an Iconia kernel.
So am I right with all the above, or am I missing something obvious, or am I just crazy (2am and my PC's made my room very hot afterall)?
Okay, so if the above is correct, couldn't/shouldn't we be doing some cooperative developement with other Honeycomb device developers? Or at least the Iconia developers, as I'm not sure about other devices. I mean, if the ROMs are pretty much compatible, all that would need to be done is have a respective kernel for the respective device flashed on-top of the ROM, right?
Anyway, laugh at me, flame me, tell me to go to bed, whatever, but I'd like to know what your thoughts are.
And on a related note:
Has anyone actually tried flashing any other "other-device ROMs" onto a TF with a TF kernel and got it working?
I'd love to try, but my internet is terrible... I swear someone else on the network constantly has their BT speeds uncapped 24/7 (share-house's are ****ty).

I think that's pretty much the goal of the CyanogenMod project. Only reason they haven't begun on a Honeycomb version is because Google never released the AOSP. Hopefully this will change with ICS.

Yes, the OEMs are working together with google behind the scenes.
More than likely Google has "forced" them to contribute code in order to participate and enjoy early code.
Unified code at the OS level would be a godsend and allow for Windows - style updates.

poltak11 said:
After seeing how the unmodified Acer Iconia Galaxy ROM + modified ASUS Transformer kernel (Clemsyn's) worked on a Transformer I started to think that this could be because of all the Honeycomb tablets are running a pretty similar OS configuration ("stock-like" Honeycomb).
Click to expand...
Click to collapse
As far as I'm aware, pretty much all the current crop of Honeycomb tablets are all based on the Nvidia Ventana reference platform, so it's not too surprising that they are all very, very, similar software-wise.
Regards,
Dave

JCopernicus said:
Yes, the OEMs are working together with google behind the scenes.
More than likely Google has "forced" them to contribute code in order to participate and enjoy early code.
Unified code at the OS level would be a godsend and allow for Windows - style updates.
Click to expand...
Click to collapse
But as the OEMs are working together, why aren't independant developers here on xda? I mean, I'm just thinking that a lot more nice work would get done if there was unified developement going on between the HC devices instead of seperate forums, and seperate ROMs that seem to be very similar.
And yes, I do agree about the closed source problem. But Google said this is just a temporary thing, right?

It's hard to write too much code when you don't have the original to start with.
No one really wants to write Honeycomb from scratch.
sassafras

sassafras_ said:
It's hard to write too much code when you don't have the original to start with.
No one really wants to write Honeycomb from scratch.
sassafras
Click to expand...
Click to collapse
I understand this, of course, but excuse my ignorance when it comes to Android Developement, but what are the developers of PRIME and Clemsyn's ROM and all the other HC ROMs working with at the moment, as there is no source other than the GPL'd kernel?

poltak11 said:
I understand this, of course, but excuse my ignorance when it comes to Android Developement, but what are the developers of PRIME and Clemsyn's ROM and all the other HC ROMs working with at the moment, as there is no source other than the GPL'd kernel?
Click to expand...
Click to collapse
They are working with the OTA. It is all compiled things. They can add things on top of it, but they can't do modifications to it because its already compiled (source code not provided).

zephiK said:
They are working with the OTA. It is all compiled things. They can add things on top of it, but they can't do modifications to it because its already compiled (source code not provided).
Click to expand...
Click to collapse
Ah, fair enough. Well assuming that Google actually does release the source-code sometime, will this sort of thing be happening? As in co-developement between devices?
It just seems like the sensible thing to be happening, as opposed to a greatly splintered "fork" style of developement.

poltak11 said:
Ah, fair enough. Well assuming that Google actually does release the source-code sometime, will this sort of thing be happening? As in co-developement between devices?
It just seems like the sensible thing to be happening, as opposed to a greatly splintered "fork" style of developement.
Click to expand...
Click to collapse
Chances are there will be a CyanogenMod type project once Android tablet sources are released.
However, there will always be developers who are primarily interested in doing their own thing, which is perfectly acceptable too.
Regards,
Dave

poltak11 said:
Ah, fair enough. Well assuming that Google actually does release the source-code sometime, will this sort of thing be happening? As in co-developement between devices?
It just seems like the sensible thing to be happening, as opposed to a greatly splintered "fork" style of developement.
Click to expand...
Click to collapse
There's a reason CM hasn't officially touched any Honeycomb tablet. There's no source. Once they open up the source with ICS then everyone will be working on it through github.

[IDEA] CM10 on N7105

Hi guys,
I think it's worth starting a separate topic for running CyanogenMod on the N7105 since we're clearly not getting our own section any time soon. I think there is a LOT of push behind getting CM10 running on the N7100 and this seems to be now progressing nicely with only a few bugs remaining. The problem is, us N7105 owners (LTE version) have been left running TW which I don't know about you but I absolutely DETEST!
As such, I figured it would be worthwhile getting all of the N7105 owners in one thread and see if we can hack together a method of getting our radio working properly on this wonderful ROM! There is another topic regarding creating a 'flashpack' but this focuses primarily on TouchWiz which isn't something I'm interested - switching TW to TW? Why bother? What I want is to run AOSP/CM on this wonderful device and enjoy the wonders of 4G with that lovely screen without all the samsung bloat and hopefully in tablet mode!
My current thinking on this is (and I intend to try this a little later today):
- Flash CM10 (N7100) - http://forum.xda-developers.com/showthread.php?t=1968949
- Flash our stock radio - backup original radio before flashing any firmware
- Flash Perseus N7105 kernel - http://forum.xda-developers.com/showthread.php?t=1927852
It would be interesting to get a complete list of what we've tried and what has/hasn't worked - that way we make it easier for both ourselves and any developers who decide to take a look at this and they can at least save some time! I did talk to 'imilka' (dev of the CM10 port) and he said he will take a look when he gets the time so that's promising at least!

chrisaw said:
My current thinking on this is (and I intend to try this a little later today):
- Flash CM10 (N7100) -
- Flash our stock radio - backup original radio before flashing any firmware
- Flash Perseus N7105 kernel -
Click to expand...
Click to collapse
Won't work as Perseus isn't an AOSP compatible kernel

D3_ said:
Won't work as Perseus isn't an AOSP compatible kernel
Click to expand...
Click to collapse
Sadly that's the conclusion I came to too - ah well, was worth a shot. It looks like part of the problem is the build.prop differences which is easily fixed. There was also mentions of differences in the paths for certain files as well as missing files for LTE usage. It does sound like this should be a very simple fix if we can compare the differences between stock N7100 and stock N7105 - surely combining the two should produce a working ROM. Then it's just a matter of finding out which specific parts are needed to get AOSP rocking.
It's a shame the stock Samsung kernel for the N7105 wont work with CM10. Any kernel devs fancy helping us out with this one?

I will compile an AOSP kernel for N7105 soon, however, it's not just the kernel, and i'm not really sure there's an easy way that you would expect to exist

imilka said:
I will compile an AOSP kernel for N7105 soon, however, it's not just the kernel, and i'm not really sure there's an easy way that you would expect to exist
Click to expand...
Click to collapse
waiting for your update

Well the current N7100 kernel does work for us - its likely just missing a few modules for LTE (if at all.)
certainly appreciate you looking in to this though!

I assume that the fact our network lock details are stored differently, and the associated dialer hidden functions don't work are link to the fact that a n7100 leaves us without signal even with our radio. I also imagine any fix would help in identifying what files needs to be changed to remove network lock.
Overall I get the imprssion our device is more similar to the USA lte versions which would be unsurprising.
I was looking into how to root, deox, etc the stock rom but I dont hace Linux running atm.
Sent from my GT-N7105 using xda app-developers app

EmptyArea said:
I assume that the fact our network lock details are stored differently, and the associated dialer hidden functions don't work are link to the fact that a n7100 leaves us without signal even with our radio. I also imagine any fix would help in identifying what files needs to be changed to remove network lock.
Overall I get the imprssion our device is more similar to the USA lte versions which would be unsurprising.
I was looking into how to root, deox, etc the stock rom but I dont hace Linux running atm.
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
That makes sense! Hopefully we can 'rally' the devs to help out - we already have one helping! It's just a shame that all we need is a few tweaks (possibly in the form of a flash-pack) and we'd be good to go and start enjoying CM10! If there's one thing I can't stand it's TouchWiz, bloated junk IMO!

EmptyArea said:
I was looking into how to root, deox, etc the stock rom but I dont hace Linux running atm.
Click to expand...
Click to collapse
You can root and deodex stock roms in Windows with cygwin and to make it even easier, you can use dsixda android kitchen.

Have to admit, I do find it extremely strange that Xda Developers forum has opted to ignore the existence of the N7105. It's very popular over here in the UK and elsewhere in the world and is set to get even more popular as LTE is adopted in more places around the globe. Would make getting developers to notice us a lot easier if we had our own forum IMO! >_<

chrisaw said:
Have to admit, I do find it extremely strange that Xda Developers forum has opted to ignore the existence of the N7105. It's very popular over here in the UK and elsewhere in the world and is set to get even more popular as LTE is adopted in more places around the globe. Would make getting developers to notice us a lot easier if we had our own forum IMO! >_<
Click to expand...
Click to collapse
Yeah man. sad case is that development for this phone model is zero to none. We are able to root n use perseus kernel bt for the only difference btween n7105 and n7100 is just the LTE and none of the roms are available to be used. Felt so left out coz of the issues in the radio firmware just coz one is lte n the other is not.
Sent from my GT-N7105 using xda premium

There is a custom rom out for the n7105
Its just not hosted on xda
Im running it with no issues
Sent from my GT-N7105 using xda premium

Got a name or URL?

Here is the link to the rom http://bbs.gfan.com/android-5285960-1-1.html
Here is the link to the download http://www.multiupload.co.uk/BZY1HLBX53
And here is its feature list
Features:
. Production based on N7105ZHALJ4 Hong Kong version of Android 4.1.1
Firmware uncompacted app
The. Using N7105ZHALJ4 original kernel
Boot Simplified Chinese
System language to Simplified Chinese, Traditional Chinese (Hong Kong & Taiwan), Korean, Chinese and English
Smart dialing retrieval
. IP dialing
. Call recording
. Calls attribution
Lunar calendar
. Blocking mode
Signed information
Support emoji expressions
. Shutdown alarm clock
Advanced Power key
Overall Deodex
With Root and Rights Management
The the Chinese access point and Chinese operators
Status bar drop-down button 15
. Lifted SMS and MMS limit
Camera selectable silent pictures.
. Join optimization script
Cancel Ringtones three seconds from weak to strong
. BusyBox
Call log removal and multimedia messages
. Shutdown sound
Join the restart tool, R.E Manager, a key lock screen
Update the Google play and Google map
. hosts file acceleration
Custom multi-window program
Sent from my GT-N7105 using xda premium

While I do appreciate that - I'm not really keen on running any form of TouchWiz on my device. I just absolutely detest the modifications Samsung made to AOSP - CM is really the ideal setup for this phone. It also means we can run true tablet mode which on a Note 2 is a fantastic experience.

I'm sorry to burst your bubble but unless N7105 becomes the only Note2 available and distribution exceeds that of N7100 the development for this device will be as limited as it is for the I9305 compared to the I9300.

victorator said:
I'm sorry to burst your bubble but unless N7105 becomes the only Note2 available and distribution exceeds that of N7100 the development for this device will be as limited as it is for the I9305 compared to the I9300.
Click to expand...
Click to collapse
With the i9305 there is a flash pack as far as I'm aware which allows you to flash i9300 ROMs and simply flash a flash-pack and i9305 kernel to allow you to run custom ROMs. This doesn't yet exist for the Note 2 and I'm not really asking for anything outlandish here - I'm just asking for CM10 on the N7105 *and* I'm even willing to throw money at this to make it happen. May be worth raising a thread for us N7105 owners to donate to developers who are supporting our device actually since while N7100 development is wonderful it doesn't benefit us in the slightest until we have a patched kernel, etc. to support AOSP/CM10 on our devices.

chrisaw said:
With the i9305 there is a flash pack as far as I'm aware which allows you to flash i9300 ROMs and simply flash a flash-pack and i9305 kernel to allow you to run custom ROMs. This doesn't yet exist for the Note 2 and I'm not really asking for anything outlandish here - I'm just asking for CM10 on the N7105 *and* I'm even willing to throw money at this to make it happen. May be worth raising a thread for us N7105 owners to donate to developers who are supporting our device actually since while N7100 development is wonderful it doesn't benefit us in the slightest until we have a patched kernel, etc. to support AOSP/CM10 on our devices.
Click to expand...
Click to collapse
I'm not aware of such thing unfortunately...maybe I missed it in the I9305 forum?
I think the case was with the S2 I9100T variant where you could just replace the modem with your T modem and still flash any standard I9100 rom.
There are many similarities between the two variants I bet, but as it turned out the I9305 doesn't have FM radio. It might not be the most important thing in the world however it points to how different the devices might actually be.

That's the same difference as the N7100 and N7105. The FM radio was replaced with an LTE radio it seems.
Have to say though, its a small price to pay for the 26Mbit speeds I'm getting from mine!

No updates on this?

Fx0/Madai Kernel: Version WTF?

The kernel source that LG posted on their opensource distribution site is not the code for the latest shipping version. Is that cool? Do they have any responsibility to provide the source for the newest version the shipped?
I wonder if the code they released matches earlier versions even. If only I could track down a rip of the system & boot images from the original version that shipped in Dec. 2014. Or even for the version after that. If anyone has one of those laying about, thanks, yo.

I have no idea, but that doesn't sound right.
Are you looking to unlock the bootloader so people can flash updated FFXOS ROMs to the device?

Saijin_Naib said:
I have no idea, but that doesn't sound right.
Are you looking to unlock the bootloader so people can flash updated FFXOS ROMs to the device?
Click to expand...
Click to collapse
Actually, I think I was wrong. Gah! I didn't realize that the prima_wlan stuff could be included included from outside the kernel tree. A qcom opensource repo is maybe where they built it from maybe?
> unlock the bootloader
No problems there, the Fx0 is wide-open. Like other LG devices, once you clear the CAF you gain Fastboot, and from there this device is splayed all day. You lose Download Mode, but since neither Mozilla or LG have seen fit to provide any of the usual KDZ images for that, I can't see any downsides. Maybe if they decide to update the Fx0 it would get used? I think it'd update in recovery instead though, yes?
Still want rips of Japanese system partition though. I wonder if the hiddenmenu is also stripped from those versions with v2.1 also? I want that hiddenmenu.

I have no idea. I'm not familiar at all with setting up a repo or anything. I've only ever build the ZTE Open repos provided by Mozilla, haha.
Oh, that is promising. What is the CAF?
Are you looking to get your Fx0 up and running with nightlies? If things actually work, I might grab one from eBay as a development/testing device as well.

Saijin_Naib said:
I have no idea. I'm not familiar at all with setting up a repo or anything. I've only ever build the ZTE Open repos provided by Mozilla, haha.
Oh, that is promising. What is the CAF?
Are you looking to get your Fx0 up and running with nightlies? If things actually work, I might grab one from eBay as a development/testing device as well.
Click to expand...
Click to collapse
Err, I meant LAF, its the partition on some LG devices where the Download Mode boot image lives. I've been spending a lot of time with my head buried in Codeaurora(CAF) repos, it's on the tip of my tongue.
Are you looking to get your Fx0 up and running with nightlies?
Click to expand...
Click to collapse
I already have to some extent. I should have a fully-functional test build any day now. Been codeblocked by some frustrating commits from Mozilla lately, broke my crap like 3 damn times in the last week. Refining the whole build setup now, trying to minimize reliance on prebuilt stuff, building as much as can, hence the interest in the pronto_wlan module, which I assumed was something that was exclusively build in the kernel tree (as seen on other LG devices), but apparently there's a CAF repo for that. Anyway, yeah.

culot said:
Err, I meant LAF, its the partition on some LG devices where the Download Mode boot image lives. I've been spending a lot of time with my head buried in Codeaurora(CAF) repos, it's on the tip of my tongue.
Click to expand...
Click to collapse
Ah, good to know. I'm a bit saddened to see that the prices on the Fx0 have gone up since just this past weekend. These must be getting more and more popular...
As an aside, you wouldn't happen to be knowledgeable about how to root the LGE LGL15G (LG Sunrise, 4.4.2, TracFone). I bought one as a beta testing device and as an Android Tablet/Wi-Fi toy, but there is no space on it due to the included bloatware O_O
culot said:
I already have to some extent. I should have a fully-functional test build any day now. Been codeblocked by some frustrating commits from Mozilla lately, broke my crap like 3 damn times in the last week. Refining the whole build setup now, trying to minimize reliance on prebuilt stuff, building as much as can, hence the interest in the pronto_wlan module, which I assumed was something that was exclusively build in the kernel tree (as seen on other LG devices), but apparently there's a CAF repo for that. Anyway, yeah.
Click to expand...
Click to collapse
I was reading on the Mozilla wiki that they've been doing some code cleanup to transition FFXOS to B2G, and to make it so the community can maintain it. Apparently, they've been a bunch of busy bees debranding everything and settling dependencies. Is this why your builds have been busted?
Do you think the Fx0 could replace the Flame as the defacto B2G development/testing device?
I'm torn between getting one for grabbing yet another ZTE Open and smashing my face against the wall trying to get it to fully work with nightly builds.
What's in that hiddenmenu? That isn't the normal developer tools menu I'm used to, right?
Is it the Blaze Initiative stuff (themeing, hacking, add-ons, mods, etc)?

Saijin_Naib said:
Ah, good to know. I'm a bit saddened to see that the prices on the Fx0 have gone up since just this past weekend. These must be getting more and more popular...
As an aside, you wouldn't happen to be knowledgeable about how to root the LGE LGL15G (LG Sunrise, 4.4.2, TracFone). I bought one as a beta testing device and as an Android Tablet/Wi-Fi toy, but there is no space on it due to the included bloatware O_O
I was reading on the Mozilla wiki that they've been doing some code cleanup to transition FFXOS to B2G, and to make it so the community can maintain it. Apparently, they've been a bunch of busy bees debranding everything and settling dependencies. Is this why your builds have been busted?
Do you think the Fx0 could replace the Flame as the defacto B2G development/testing device?
I'm torn between getting one for grabbing yet another ZTE Open and smashing my face against the wall trying to get it to fully work with nightly builds.
What's in that hiddenmenu? That isn't the normal developer tools menu I'm used to, right?
Is it the Blaze Initiative stuff (themeing, hacking, add-ons, mods, etc)?
Click to expand...
Click to collapse
Do you think the Fx0 could replace the Flame as the defacto B2G development/testing device?
Click to expand...
Click to collapse
Considering how much proprietary LG stuff is on the Fx0, I doubt it. Dunno. Since FxoS is transitioning to B2G is there even a need for a official dev device? I have no idea really.
What's in that hiddenmenu? That isn't the normal developer tools menu I'm used to, right?
Click to expand...
Click to collapse
Just the usual LG-specific hiddenmenu stuff. It seems like it was included in the initial release version for the Fx0... but from there, I don't know. Too bad I can't find any of the previous versions anywhere. Somebody must have them, somewhere.
Is it the Blaze Initiative stuff (themeing, hacking, add-ons, mods, etc)?
Click to expand...
Click to collapse
I have no idea what that is. Tell me more!
root the LGE LGL15G
Click to expand...
Click to collapse
No, I don't know anything about that. I did try one once, seemed like a decent value for the $15 or so it was selling for.

culot said:
Considering how much proprietary LG stuff is on the Fx0, I doubt it. Dunno. Since FxoS is transitioning to B2G is there even a need for a official dev device? I have no idea really.
Click to expand...
Click to collapse
Drat. I was hoping they (LG) had opened up some of the binary blobs in their source release. I guess you're right in that there is no need for an official dev device, but much like with LuneOS, I think there is a need for a "supported" target/reference device that sets the baseline for functionality. I was hoping the Fx0 could be this device, but with your evaluation of it being still a highly closed, it sounds like a poor choice.
culot said:
Just the usual LG-specific hiddenmenu stuff. It seems like it was included in the initial release version for the Fx0... but from there, I don't know. Too bad I can't find any of the previous versions anywhere. Somebody must have them, somewhere.
Click to expand...
Click to collapse
I've never seen this menu. Do the new Fx0 devices sold on eBay have this OS image installed, or is it something that was only shipped on the KDDI carrier sold devices?
culot said:
I have no idea what that is. Tell me more!
Click to expand...
Click to collapse
The Blaze initiative was a path Mozilla were looking to take FireFoxOS on by allowing the OS to be customized and tweaked much like the desktop browser. The device would have the ability to call up the DevTools to edit the code of any running webapp to modify the appearance and functionality of the program. From what I had read, this would extend to even privileged/system apps. In this manner, the user could add something to say the Messages app (like a timestamp for how late a message arrived), change the background color of the messages thread, etc. These add-ons could be submitted to the Marketplace for certification and download. Also, it was likely that users could directly share these modifications by Sharing activities including Email, SMS, etc.
There was also talk of migrating over various XUL add-ons from the desktop browser that would be compatible with FFXOS. That alone would have made the platform borderline unstoppable, as the possibilities for expansion of utility, safety, and aesthetics would be nearly endless.
All of this being said, I can't currently find the articles about this initiative anymore. I'll keep looking.
culot said:
No, I don't know anything about that. I did try one once, seemed like a decent value for the $15 or so it was selling for.
Click to expand...
Click to collapse
I got mine for $9.99, and it benches out to being fairly comparable to the Moto E, which is not a bad performance point to be at for around $10. Shame it is SIM-locked and very difficult to root and take the garbageware out of.

Saijin_Naib said:
I've never seen this menu. Do the new Fx0 devices sold on eBay have this OS image installed, or is it something that was only shipped on the KDDI carrier sold devices?.
Click to expand...
Click to collapse
It looks like maybe the hiddenmenu was removed with a FxOS v2 update that added the ability to edit APNs, something that had to be done in the hiddenmenu previsouly. Maybe...

Ah, crap, I was wrong: the hiddenmenu, along with a ton of other LG & KDDI stuff, was stripped out of the international/unlocked version, leaving it a slow, featureless shell. It's disgusting actually. I feel acutely slighted. It's amazing the difference between both the speed and the features of the Japanese and unlocked versions. Apparently in Japan this is actually a decent phone. Too bad the international/unlocked peeps got the shaft.
And here I thought FxOS in general was just slow and terrible: turns out that was just result of the hatchet job pulled on the unlocked variants of the Fx0.
I wonder if it would be possible to overcome the mozfree issue that prevents the old libs from working on newer B2G?
Gah! I feel angry.

Hey. Do you still want the original jap 2.0 images?

aflaton said:
Hey. Do you still want the original jap 2.0 images?
Click to expand...
Click to collapse
If you have a retail firmware, it would be much appreciated.